Hi

I am just starting to consider Database Change Tracking, initial investigations vs. replication. Does 4.0 cover this functionality?

Reason i ask is that replication is Subscriber Only in SQL Express 2012, however it does support Change Tracking, so i can build my own 'replication' for nightly updates back to the main database.

Thanks

Steven

What exactly do you mean with database change tracking and in what light should it be supported in our system? (designer or runtime or both?)

Hi Otis

Change Tracking is like a knock-off of replication, but unlike replication it allows two-way synchronisation from within applications using SQL Express, whereas Express can only be a Subscriber when using normal replication.

"Returns change tracking information for a table.You can use this statement to return all changes for a table or change tracking information for a specific row." Syntax for changetable command: http://technet.microsoft.com/en-us/library/bb934145.aspx

It's not a standard Select command?

Thanks

Steven

Ah I see.

I think the best way is to create a simple stored procedure which calls this function and returns the results you need. It's a table valued function but it requires input of a table, which is a structure we can't provide from client to DB. The stored proc is then mappable from the designer so you can call it from within your code.

Thanks Otis, i'll have a look at that.

Cheers

Steven