In continuing from the series of Change-Data-Capture tags on this site I have been testing through this CDC feature on my test environment, which has proved fruitful results (to some extent). But the in the real world scenario do you really need to log all such activites? As you may be aware that logging...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
02-01-2008
Filed under: sql server, users, ctp, environment, cdc, best practice, testing, triggers, new features, audit trial, change data capture, stored procedures
To provide High Availability feature within your database environment you could take advantage of Database Mirroring when using SQL Server 2005. As with all critical databases, minimizing data loss and downtime are of the highest importance. Having "AlwaysOn" configuration within the SQL Server...
Continuing on the MAX WORKER THREADS topic from ThisBlog I have been asked about method of calculating the amount of system resources that will be used when the setting is increased to 500 from 255 (default). Well, as one of the best practices you must test the implications and usage in hiking such a...
Posted to
SQLServer-QA.net - Knowledge Sharing Network (SSQA.net)
(Weblog)
by
Anonymous
on
11-15-2007
Filed under: sql server, performance, microsoft, server, tuning, dbcc, system, best practice, testing, resources, sqlperf, max worker threads
You may be aware that plan guides will help the optimizer to perform better and a general recommendation is to use the relevant USE PLAN query hint when the other standard query tuning options are failed. It is also necessary to test through the results you would expect are not upto the mark, when using...