October 2008 Blog Posts
I was recently doing a little research on scaling out SQL Server Reporting Services and found these articles. I thought I'd share them with you here (and so I could quickly find them again later if I needed to).
http://sqlcat.com/technicalnotes/archive/2008/06/05/reporting-services-scale-out-architecture.aspx
http://msdn.microsoft.com/en-us/library/ms159114.aspx
http://msdn.microsoft.com/en-us/library/ms156453.aspx
http://download.microsoft.com/download/e/8/e/e8e1737a-e246-472d-bf4a-8ac89bae8c9e/SQL%20Server%202008%20Performance%20and%20Scale%20WhtPaper.pdf
http://sqlcat.com/technicalnotes/archive/2008/07/09/scaling-up-reporting-services-2008-vs-reporting-services-2005-lessons-learned.aspx
Got any other useful resources or white papers? Please share them as a comment below.
Enjoy!
Joe
Early this morning, Bob Ward of Microsoft PSS SQL Support fame authored a post on the PSS Support blog entitled "SQL Server Support in a Hardware Virtualization Environment". As always, Bob's comments are helpful. In the post, he clarifies and elaborates on Microsoft's official position on support for a SQL Server system in a Virtualized environment.
I normally just twitter interesting links such as this, however given all of the questions and uncertainty of virtualization recently, I thought this on warranted its own blog post, too.
Here's the link - http://blogs.msdn.com/psssql/archive/2008/10/08/sql-server-support-in-a-hardware-virtualization-environment.aspx
Cheers!
Joe
Sometimes it's useful to disable one or more constraints on a table, do something significant, and then re-enable the constaint(s) after you're done. This is most often done to improve performance during a bulk load operation.
According to SQL Server Books Online, we can disable constraints using the ALTER TABLE statement.Here's an excerpt from SQL Server Books Online that describes it.
{ CHECK | NOCHECK } CONSTRAINT
Specifies that constraint_name is enabled or disabled. This option can only be used with FOREIGN KEY and CHECK constraints. When NOCHECK is specified, the constraint is disabled and future inserts or updates...