Tag Info

Hot answers tagged

4

Some of the implementation specifics depend on exactly what type of behaviour you need from this table (e.g. FIFO), but a typical design for a queue table uses DELETE with an OUTPUT clause: DELETE TOP (n) FROM QueueTable WITH (ROWLOCK, READPAST) OUTPUT deleted.RecordID; Or if ordered removal is required: DELETE FROM ( SELECT TOP (n) RecordID FROM ...


2

http://technet.microsoft.com/en-us/library/hh710064.aspx talks about monitoring Change Tracking, however it neglects to mention anything about performance other than "Change Tracking is lightweight". It seems you're out of luck...


2

I have been able to find the documentation that I was looking for. CDC is supported off of the readable secondary but Change Tracking is not unfortunately. The link is specified below but here are the relevant parts for my needs. Redirecting the Query Load to a Readable Secondary While in many cases a client application will always want to connect to ...


2

No, there isn't any. Any sort of 'last updated at' tracking would run into a severe performance problem as all updates, from all transactions, would attempt to update the one record tracking the 'last updated at'. This would effectively mean only one transaction can update the table at any moment, and all other transactions have to wait for the first one to ...


1

If the source is insert-only give it an IDENTITY column. When you do your data transfer you log the highest value written across. During the next transfer you need only query for values greater than that logged during the previous transfer. We do this for transferring log records to a data warehouse. For updatable rows add a "dirty" flag. It will have ...


1

Don't be tempted to re-invent the wheel. This problem has been solved many times before you came across it. Take a look at schema comparison tools, such as those available in SQL Server Data Tools (SSDT), and commercial options like Red-Gate SQL Compare. Going forward you can also use DDL Triggers to log certain DDL events, helping you catch outlying ...


1

This sounds like a situation where Oracle Change Data Capture would be appropriate. You would need to write some code that would subscribe to changes to this table and process them by pushing the changes to your SAP BW system. You can also use Oracle Streams to do heterogeneous replication from Oracle to a non-Oracle database using an Oracle Transparent ...



Only top voted, non community-wiki answers of a minimum length are eligible