<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Cindy Gross - Troubleshooting, tips, and general advice about SQL Server</title><link>http://blogs.msdn.com/cindygross/default.aspx</link><description /><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Backing up a corrupted SQL Server database</title><link>http://blogs.msdn.com/cindygross/archive/2009/12/02/backing-up-a-corrupted-sql-server-database.aspx</link><pubDate>Wed, 02 Dec 2009 16:33:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9931561</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9931561.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9931561</wfw:commentRss><description>I had a question about how to do a backup and skip a corrupted block of data. First, DO NOT DO IT unless you absolutely have to, such as when you are taking a backup prior to trying to fix the corruption (which means you should be on the phone with Microsoft...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/12/02/backing-up-a-corrupted-sql-server-database.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9931561" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/checksum/default.aspx">checksum</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/corruption/default.aspx">corruption</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/backup/default.aspx">backup</category></item><item><title>Compilation of SQL Server TempDB IO Best Practices</title><link>http://blogs.msdn.com/cindygross/archive/2009/11/20/compilation-of-sql-server-tempdb-io-best-practices.aspx</link><pubDate>Fri, 20 Nov 2009 17:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9926308</guid><dc:creator>CindyGross</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9926308.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9926308</wfw:commentRss><description>It is important to optimize TempDB for good performance. In particular, I am focusing on how to allocate files. TempDB is a unique database in several ways. The ones most relevant to this discussion are: · It is often one of the busiest databases on an...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/11/20/compilation-of-sql-server-tempdb-io-best-practices.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9926308" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/tempdb/default.aspx">tempdb</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/IO/default.aspx">IO</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/best+practices/default.aspx">best practices</category></item><item><title>SQL Server and Fragmentation</title><link>http://blogs.msdn.com/cindygross/archive/2009/11/20/sql-server-and-fragmentation.aspx</link><pubDate>Fri, 20 Nov 2009 16:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9926303</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9926303.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9926303</wfw:commentRss><description>There are several types of fragmentation that affect SQL Server, all of which have the potential to cause performance problems. 1) At the disk/OS level individual files can become fragmented due to growth over time. This can be addressed by a defragmentation...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/11/20/sql-server-and-fragmentation.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9926303" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/performance/default.aspx">performance</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/defragment/default.aspx">defragment</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/fragmentation/default.aspx">fragmentation</category></item><item><title>SQL Server 2008 setup may report a Windows 2008 cluster validation failure</title><link>http://blogs.msdn.com/cindygross/archive/2009/11/20/sql-server-2008-setup-may-report-a-windows-2008-cluster-validation-failure.aspx</link><pubDate>Fri, 20 Nov 2009 16:55:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9926299</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9926299.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9926299</wfw:commentRss><description>You may receive the error "The cluster either has not been verified or there are errors or failures in the verification report" while installing a SQL Server clustered installation on Windows 2008. When see this error you must fix the underlying error...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/11/20/sql-server-2008-setup-may-report-a-windows-2008-cluster-validation-failure.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9926299" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server/default.aspx">sql server</category><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+setup/default.aspx">sql server setup</category></item><item><title>How to tell what edition your SQL Server setup files are</title><link>http://blogs.msdn.com/cindygross/archive/2009/11/20/how-to-tell-what-edition-your-sql-server-setup-files-are.aspx</link><pubDate>Fri, 20 Nov 2009 16:49:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9926296</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9926296.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9926296</wfw:commentRss><description>The setup files for SQL Server look pretty much the same for all editions. If you saved the files somewhere but didn't indicate in your directory name or a readme file which edition they are for, how do you tell the edition? Running setup doesn't necessarily...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/11/20/how-to-tell-what-edition-your-sql-server-setup-files-are.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9926296" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+setup/default.aspx">sql server setup</category></item><item><title>How to use PsGetSid for SQL Server</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/29/how-to-use-psgetsid-for-sql-server.aspx</link><pubDate>Fri, 30 Oct 2009 03:38:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9915093</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9915093.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9915093</wfw:commentRss><description>To translate a SID to a name or vice versa, you can use this tool from sysinternals: PsGetSid v1.43 http://technet.microsoft.com/en-us/sysinternals/bb897417.aspx You can use it to translate the SID in these registry keys into the SQL Domain Groups or...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/29/how-to-use-psgetsid-for-sql-server.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9915093" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server/default.aspx">sql server</category></item><item><title>Checklist for upgrading to a new version of SQL Server</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/28/checklist-for-upgrading-to-a-new-version-of-sql-server.aspx</link><pubDate>Wed, 28 Oct 2009 23:22:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9914421</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9914421.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9914421</wfw:commentRss><description>Here is the basic process for a full version upgrade (such as 2000 to 2008) of the SQL Server engine. The steps will be different for RS or AS. I did not include all the details of variations such as replication, mirroring, log shipping, full-text search,...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/28/checklist-for-upgrading-to-a-new-version-of-sql-server.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9914421" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+upgrade/default.aspx">sql server upgrade</category></item><item><title>How People Abuse Their SQL Server Transaction Log - Things NOT to Do</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/28/how-people-abuse-their-sql-server-transaction-log-things-not-to-do.aspx</link><pubDate>Wed, 28 Oct 2009 20:47:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9914322</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9914322.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9914322</wfw:commentRss><description>Care and Feeding of the Transaction Log Want to learn more about how the transaction log works? Kalen Delaney, celebrated author of SQL Server 2008 Internals and the Inside SQL Server series as well as a world class trainer and performance tuner, is giving...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/28/how-people-abuse-their-sql-server-transaction-log-things-not-to-do.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9914322" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+2005+2008+transaction+log+logging/default.aspx">sql server 2005 2008 transaction log logging</category></item><item><title>Considerations for installing SQL Server on VMWare</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/23/considerations-for-installing-sql-server-on-vmware.aspx</link><pubDate>Fri, 23 Oct 2009 22:15:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9912285</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9912285.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9912285</wfw:commentRss><description>You still need to follow the standard SQL Server best practices, security, and preparation when you install on a VMware VM. Below are some additional considerations with regards to VMware. Key points: · You must double check that your combination of VMWare,...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/23/considerations-for-installing-sql-server-on-vmware.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9912285" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+on+vmware/default.aspx">sql server on vmware</category></item><item><title>Checklist for installing SQL Server 2005 as a clustered instance</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/23/checklist-for-installing-sql-server-2005-as-a-clustered-instance.aspx</link><pubDate>Fri, 23 Oct 2009 22:06:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9912281</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9912281.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9912281</wfw:commentRss><description>Checklist for installing SQL Server 2005 as a clustered instance Windows/Hardware 1) Verify the Windows cluster is set up per basic best practices and that basic failover works. 2) Verify you have the latest patches, especially security patches, for Windows....(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/23/checklist-for-installing-sql-server-2005-as-a-clustered-instance.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9912281" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+serverver+2005+windows+cluster/default.aspx">sql serverver 2005 windows cluster</category></item><item><title>SQL Server and TCP Chimney</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/22/sql-server-and-tcp-chimney.aspx</link><pubDate>Thu, 22 Oct 2009 19:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9911644</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9911644.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9911644</wfw:commentRss><description>If you are using SQL Server or Analysis Services: I suggest you double check that your SNP settings, especially TCP Chimney Offset, are all OFF unless your NIC vendor has verified they support it and you have installed their version of drivers that support...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/22/sql-server-and-tcp-chimney.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9911644" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+tcp+chimney+snp/default.aspx">sql server tcp chimney snp</category></item><item><title>There is still time to register for the 2009 SQL PASS Summit</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/19/there-is-still-time-to-register-for-the-2009-sql-pass-summit.aspx</link><pubDate>Mon, 19 Oct 2009 20:22:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9909403</guid><dc:creator>CindyGross</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9909403.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9909403</wfw:commentRss><description>If you are considering going to SQL PASS this year Nov 2-5 there are several different discounts available for the main conference (Tues, Wed, Thu). You can only use one of the discounts, you can NOT add them together. I will be at PASS, and I hope to...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/19/there-is-still-time-to-register-for-the-2009-sql-pass-summit.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9909403" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+sql+pass+conference+2009/default.aspx">sql server sql pass conference 2009</category></item><item><title>How to automate Update Statistics</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/16/how-to-automate-update-statistics.aspx</link><pubDate>Fri, 16 Oct 2009 22:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9908415</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9908415.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9908415</wfw:commentRss><description>For SQL Server 2005 here are some options to update statistics with the default settings that samples the data instead of reading every row: 1) If you are also defragmenting your database with REBUILD and/or REORGANIZE you will want to integrate your...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/16/how-to-automate-update-statistics.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9908415" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+update+statistics+index+maintenance/default.aspx">sql server update statistics index maintenance</category></item><item><title>SQL Server with NetApp SAN</title><link>http://blogs.msdn.com/cindygross/archive/2009/10/16/sql-server-with-netapp-san.aspx</link><pubDate>Fri, 16 Oct 2009 22:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9908411</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9908411.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9908411</wfw:commentRss><description>If you are planning to use NetApp as the SAN for your SQL Server instance(s), take a look at these documents in addition to the normal SQL Server IO planning best practices documents. TR-3779 Sizing best practice guide. http://media.netapp.com/documents/tr-3779.pdf...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/10/16/sql-server-with-netapp-san.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9908411" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+on+netapp+san+net+app+io/default.aspx">sql server on netapp san net app io</category></item><item><title>SQL Server Security Granularity</title><link>http://blogs.msdn.com/cindygross/archive/2009/09/02/sql-server-security-granularity.aspx</link><pubDate>Thu, 03 Sep 2009 02:10:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9890634</guid><dc:creator>CindyGross</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/cindygross/comments/9890634.aspx</comments><wfw:commentRss>http://blogs.msdn.com/cindygross/commentrss.aspx?PostID=9890634</wfw:commentRss><description>I have had some questions recently about how to grant developers certain permissions without giving them sysadmin rights. Hopefully this summary will help you determine how to grant the least possible privileges. The summary is based on SQL Server 2005...(&lt;a href="http://blogs.msdn.com/cindygross/archive/2009/09/02/sql-server-security-granularity.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9890634" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/cindygross/archive/tags/sql+server+2005+2008+security+granular+granularity+permissions+grant+revoke+deny/default.aspx">sql server 2005 2008 security granular granularity permissions grant revoke deny</category></item></channel></rss>