Wisteria leaves in winter.
SQL Server has a process called replication, whereby you can automatically copy records from one database to another, and keep them in-sync. One use for this is to have one database as the transactional database, and another to report from, with the reporting database having indexes and constraints tailored more toward faster reporting (reads) than fast input.
Sometimes replication gets a little behind, and if you are running reports on the database that is a little behind, you might like to know.
The stored procedure sp_replcounters will tell you the count of transactions awaiting transfer to the distribution database (which lies between the transaction database and the destination database in a replication process). You can call this stored procedure, but you want it to return the result set to Java.
One way to achieve this is to wrap your own stored procedure around it, put the records into a temp table and query the temp table to return the result set. This only works if you specify SET NOCOUNT ON, otherwise the Java Persistence API (JPA) gets confused by the multiple queries and you don’t get the result set in your Java code.
CREATE PROCEDURE GetReplicationLatency
--This is important. Results from multiple queries within stored procedures throw JPA off unless SET NOCOUNT ON is used.
SET NOCOUNT ON
declare @db varchar(50)
set @db = db_name()
create table #tempTable ([database] varchar(50), [replicated transactions] int, [replication rate trans/sec] int,
[replication latency (sec)] decimal(16,6), replbeginlsn varchar(40), replnextlsn varchar(40))
insert into #tempTable
select * from #tempTable where [database] = @db
drop table #tempTable
Then your Java code looks like this:
private static final String REPLICATION_LATENCY_QUERY = "exec GetReplicationLatency ";Query query = getEntityManager().createNativeQuery(REPLICATION_LATENCY_QUERY);
Query query = getEntityManager().createNativeQuery(REPLICATION_LATENCY_QUERY);
List<Object> results = query.getResultList();
That’s a pic of me with Thor.
I had a situation come up where every time a particular table was updated, an indexed view was also getting updated. That view was intended to speed up a report, but it made the table update really horrible. The view would only get updated if one particular column in the table was being updated. That column never got updated through the application, because once the record was created that column’s input field got grayed out. But Hibernate’s default behavior is to update all columns rather than to check which ones changed and only update the changed columns.
There is a performance trade-off. Usually you probably want the default behavior. But in this case, definitely not.
But Hibernate has an option to allow for updating only the columns that changed. This option is called dynamic-update. Different versions of Hibernate implement it differently. In the example in this blog post, hibernate-annotations version 3.4.0.GA was the dependency brought in.
Because Hibernate’s org.hibernate.annotations.Entity class is not a replacement, but rather a supplementation of javax.persistence.Entity, you have to implement it like this:
@org.hibernate.annotations.Entity(dynamicUpdate = true, selectBeforeUpdate = true)
@Table(name = "blah")
public class Blah...
The selectBeforeUpdate option is not required with the dynamicUpdate. It basically states that before doing an update, do a select to make sure you have the most recent copy of the table, then the dynamicUpdate option says only update changed columns.
Uses joda-time (because yes, I still work in Java 1.6). There is probably a simpler way. But this works. This assumes all parts of the string are supplied.
public static Date convertUTCStringToLocalDateTime(String utcDate)
DateTime utcDateTime = new DateTime(utcDate);
Date localDateTime = utcDateTime.toDate();
Needed to parse an XML import file in a Java application. I liked what I read about JAXB here, so this is the XML parser I used. What I liked about it is that I didn’t need to write code to deal with the XML file line-by-line. With JAXB, you do a little prep work to create a schema for the XML file, and at run-time the JAXB methods just need to know the location of the XML file and the location of the class definitions and it creates your Java objects. Then you just deal with these objects in your Java code however you please. Not a lot of fuss involved.
Creating the schema
First step is to create a schema from your XML file. I used a free online schema generator. I just uploaded my XML file and it created an XSD schema for me.
Creating classes (called binding the schema)
The Java SDK comes with a tool for this. You don’t need to download or install anything that you don’t already have. The tool is xjc, and it’s in Java’s bin folder. You can type xjc -help to learn about all the options. But the main syntax you need is this:
xjc -d <directory to create Java class files in> -p <package name to use in the class files> <schema created in previous step with a .xsd file extension>
You need these imports:
JAXBContext jaxbContext = JAXBContext.newInstance(location of classes you created using the xjc tool);
Unmarshaller unmarshaller = jaxbContext.createUnmarshaller();
Object o = unmarshaller.unmarshal(new File(location and name of XML file to parse));
You can cast the output to the object type immediately if you’re only using this code for one type of XML file and you know what type of object it will always generate. Or leave it as an Object if you want this to handle any XML file, and then later check the type of object with instanceof .