Tag Info

New answers tagged

0

I solved this issue using a non-free ORM http://www.devart.com/dotconnect/postgresql/articles/tutorial_ef.html


2

We've used Change Tracking to handle this. We've found it lightweight and easy to set up and administer. The largest system's moving tens of thousands of rows (from a table containing millions) per day without signs of stress. Of course your configuration will dictate your throughput. It's big cousin - Change Data Capute - will handle the case where you ...


0

The "best way" is a matter of opinion, but I've previously created separate logging tables on which I've built custom reports. The logging tables can be populated by the application or using triggers. If your application (app or stored procedures) does the logging you will have to identify and modify each and every bit of code that performs those updates ...


2

Is the default setting for Sql Server comparable to "innodb_flush_log_at_trx_commit = 1" or to "innodb_flush_log_at_trx_commit = 2"? No. Assuming similar hardware, SQL Server should be just as slow as MySQL, since both would have to flush the commit for every row. Therefore there must be something else at play, very likely in the (not posted) C# code ...



Top 50 recent answers are included