<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblogcasts.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Andrew Calvett &lt;a href="http://www.linkedin.com/in/andrewcalvett"&gt;&lt;img src="http://www.linkedin.com/img/webpromo/btn_liprofile_blue_80x15.gif" width="80" height="15" border="0" alt="View Andrew Calvett&amp;#39;s profile on LinkedIn" /&gt;&lt;/a&gt;</title><subtitle type="html" /><id>http://sqlblogcasts.com/blogs/acalvett/atom.aspx</id><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/default.aspx" /><link rel="self" type="application/atom+xml" href="http://sqlblogcasts.com/blogs/acalvett/atom.aspx" /><generator uri="http://communityserver.org" version="3.1.20917.1142">Community Server</generator><updated>2007-09-14T15:31:00Z</updated><entry><title>Exploring backup read io performance</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2010/01/24/exploring-backup-read-io-performance.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2010/01/24/exploring-backup-read-io-performance.aspx</id><published>2010-01-24T14:12:00Z</published><updated>2010-01-24T14:12:00Z</updated><content type="html">I was recently exploring how to increase the backup read throughput on one of our SQL servers. Below are some interesting facts i found. I would say that one of the most important reminders that came from the exercise is, do not assume that 2 databases being backup up on the same server using an identical backup command means that the processes are identical under the hood. Backup read threads are spawned 1 per physical device used by the database. (This is documented in Optimising Backup &amp;amp; Restore...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2010/01/24/exploring-backup-read-io-performance.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=12909" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="Performance" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Performance/default.aspx" /><category term="Database Engine" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Database+Engine/default.aspx" /><category term="2008" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/2008/default.aspx" /></entry><entry><title>Enter the SSAS server level lock......</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/11/23/enter-the-ssas-server-level-lock.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2009/11/23/enter-the-ssas-server-level-lock.aspx</id><published>2009-11-23T18:13:00Z</published><updated>2009-11-23T18:13:00Z</updated><content type="html">Ok, so your reaction to the title is probably the same as mine when i found out about SSAS server level locks! So, i will give you the scripts to reproduce the server level lock but first lets get down to business…. :) Server locks were introduced in one of the SP2 cumulative updates. At the moment i can say it was pre CU12. I`m not sure why it was introduced but it likely to be in response to a “feature” :) Fortunately the lock only appears at the end of processing when SSAS commits its data and...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/11/23/enter-the-ssas-server-level-lock.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=12534" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="Performance" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Performance/default.aspx" /><category term="SSAS 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SSAS+2005/default.aspx" /><category term="Analysis Services" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Analysis+Services/default.aspx" /><category term="Hanging" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Hanging/default.aspx" /><category term="SSAS" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SSAS/default.aspx" /><category term="Locking" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Locking/default.aspx" /></entry><entry><title>SSAS 2008 - INI Files and in place upgrades</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/09/24/SSAS-2008-_2D00_-INI-files-and-in-place-upgrades.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2009/09/24/SSAS-2008-_2D00_-INI-files-and-in-place-upgrades.aspx</id><published>2009-09-24T21:13:00Z</published><updated>2009-09-24T21:13:00Z</updated><content type="html">Being the suspicious person i am i wondered if there would be any differences in the MSMDSRV.ini of an instance upgraded from 2005 as opposed to a clean install. Now obviously i expect an in place upgrade to preserve my settings and add any new ones because it should not overwrite anything since i might have change from defaults for a good reason……. Below is what i found followed by my thoughts…. IN Place Upgrade Value (Effectively 2005) &amp;lt;ServerSendTimeout&amp;gt;-1&amp;lt;/ServerSendTimeout&amp;gt; &amp;lt;ServerReceiveTimeout&amp;gt;...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/09/24/SSAS-2008-_2D00_-INI-files-and-in-place-upgrades.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=12338" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="SSAS 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SSAS+2005/default.aspx" /><category term="Analysis Services" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Analysis+Services/default.aspx" /><category term="SSAS" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SSAS/default.aspx" /><category term="2008" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/2008/default.aspx" /></entry><entry><title>The cost of SSAS metadata management</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/08/21/the-cost-of-ssas-metadata-management.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2009/08/21/the-cost-of-ssas-metadata-management.aspx</id><published>2009-08-21T05:45:00Z</published><updated>2009-08-21T05:45:00Z</updated><content type="html">This post will explain how we found ourselves in a situation where when processing a partition the metadata checks took 50 times longer than the actual partition and how to identify what time penalty you are incurring for the metadata checks. The system i was investigating had around 80 cubes with around 100 partitions per cube all hosted in one database and we would add 1 partition per cube per day. The partitions in each cube were small but were taking far to long to process and as each day passed...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/08/21/the-cost-of-ssas-metadata-management.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=12155" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="Performance" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Performance/default.aspx" /><category term="SSAS 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SSAS+2005/default.aspx" /><category term="Analysis Services" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Analysis+Services/default.aspx" /></entry><entry><title>Analysis Server appears to hang…..</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/04/05/analysis-server-appears-to-hang.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2009/04/05/analysis-server-appears-to-hang.aspx</id><published>2009-04-05T20:40:00Z</published><updated>2009-04-05T20:40:00Z</updated><content type="html">We had an ongoing problem where by users would suddenly start complaining that the Analysis Server was hanging. When investigating the box we could see that there appeared to be no physical constraints. Disks were a bit above average, CPU was very low and there was plenty of memory. When looking at the server through the SSAS activity viewer (part of the community samples) we could see that users were definitely queuing up and many of the queries should have returned in less than a second but were...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/04/05/analysis-server-appears-to-hang.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=11522" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="Performance" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Performance/default.aspx" /><category term="SSAS 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SSAS+2005/default.aspx" /><category term="Analysis Services" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Analysis+Services/default.aspx" /><category term="MDX" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/MDX/default.aspx" /><category term="Hanging" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Hanging/default.aspx" /></entry><entry><title>The evils of implicit conversions</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/01/18/the-evils-of-implicit-conversions.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2009/01/18/the-evils-of-implicit-conversions.aspx</id><published>2009-01-18T17:18:00Z</published><updated>2009-01-18T17:18:00Z</updated><content type="html">I wanted to put up a brief post showing the impact of an implicit conversion on the performance of a query (or not......). In the example i will show an implicit conversion negatively impacting query performance and an implicit conversion that does not impact performance..... So, we need to setup the test environment using the code below. SET ANSI_WARNINGS OFF --******** Create Test Data ****************** CREATE TABLE #data_test ( ukey I NT IDENTITY ( 1 , 1 ) PRIMARY KEY , first VARCHAR ( 200 )...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2009/01/18/the-evils-of-implicit-conversions.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=11232" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="SQL 2000" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2000/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="Performance" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Performance/default.aspx" /></entry><entry><title>The overhead of a non-unique clustered index</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/10/20/the-overhead-of-a-non-unique-clustered-index.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2008/10/20/the-overhead-of-a-non-unique-clustered-index.aspx</id><published>2008-10-19T23:21:00Z</published><updated>2008-10-19T23:21:00Z</updated><content type="html">So, we all know that if we create a clustered index that is not unique that we will incur a 4 byte overhead right? Well not always because as usual, it depends..... When you create a non-unique clustered index SQL server must maintain uniqueness so it adds a hidden 4 byte column which is populated for each non-unique row (not every row) but what many people may not realise is that this is actually a variable length column so if your table has no variable length columns you have to incur another 4...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/10/20/the-overhead-of-a-non-unique-clustered-index.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=10917" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="SQL 2000" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2000/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="Database Engine" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Database+Engine/default.aspx" /></entry><entry><title>Changing the Data Files Location after Installation</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/08/10/Changing-the-data-files-location-after-installation.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2008/08/10/Changing-the-data-files-location-after-installation.aspx</id><published>2008-08-10T09:28:00Z</published><updated>2008-08-10T09:28:00Z</updated><content type="html">The other day i wanted to change the &amp;quot;Data Files&amp;quot; location for a 2005 database engine installation and a 2005 Analysis Services installation which you can specify under the advanced options during installation. I quickly found out that there appears to be no documented ways to do this other than uninstall SQL Server and install again specifying a new location for data files. It&amp;#39;s also not as simple as moving your system databases as &amp;quot;Data files&amp;quot; covers things like server errors...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/08/10/Changing-the-data-files-location-after-installation.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=10703" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="Analysis Services" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Analysis+Services/default.aspx" /><category term="Database Engine" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Database+Engine/default.aspx" /></entry><entry><title>MS SQL Server Book of Wisdom</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/05/21/ms-sql-server-book-of-wisdom.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2008/05/21/ms-sql-server-book-of-wisdom.aspx</id><published>2008-05-21T17:07:00Z</published><updated>2008-05-21T17:07:00Z</updated><content type="html">I was chatting with a friend today and he asked “Have you ever seen those little books of wisdom?&amp;quot;. We quickly decided that we could write a MS SQL Book of Wisdom, Below is a summary of what ensued for your amusement. Now, some of the statements are actually based on bad real life advice and many we just made up. Can you tell which is which? Also please comment if you have got any good entries for the Book….. Why would i want my server to be enabled for awe!? I`m already in awe of my coding...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/05/21/ms-sql-server-book-of-wisdom.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=10421" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="Just for fun" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Just+for+fun/default.aspx" /></entry><entry><title>SSAS 2005 – Server side tracing starter kit</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/04/07/SSAS-2005-Server-side-tracing-starter-kit.aspx" /><link rel="enclosure" type="application/x-rar-compressed" length="1563" href="http://sqlblogcasts.com/blogs/acalvett/attachment/10305.ashx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2008/04/07/SSAS-2005-Server-side-tracing-starter-kit.aspx</id><published>2008-04-07T21:32:00Z</published><updated>2008-04-07T21:32:00Z</updated><content type="html">Analysis services 2005 (SSAS) added the ability to trace server side events and i have used this feature a number of times. To date i had always used the profiler gui to do the SSAS tracing but today i found myself needing to initiate and manage a trace with scripts. The good news is that it can be done! It did take a while to piece together how to do it though and i found some of the information quite a challenge to find so i am sharing with you the results and have attached a zip file with the...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/04/07/SSAS-2005-Server-side-tracing-starter-kit.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=10305" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="Tools" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tools/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="Performance" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Performance/default.aspx" /><category term="SSAS 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SSAS+2005/default.aspx" /><category term="Analysis Services" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Analysis+Services/default.aspx" /></entry><entry><title>Transaction log backup deadlock</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/02/19/transaction-log-backup-deadlock.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2008/02/19/transaction-log-backup-deadlock.aspx</id><published>2008-02-19T23:10:00Z</published><updated>2008-02-19T23:10:00Z</updated><content type="html">Recently we started to see deadlock errors when backing up our transaction logs. The "important" part of the error is shown below. Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful. What this meant was that the transaction log backup was occurring but the entry in the msdb was not being made as it was being chosen as a deadlock victim so we investigated the cause of...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/02/19/transaction-log-backup-deadlock.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=7530" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="Maintenance Plans" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Maintenance+Plans/default.aspx" /><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="System Procedures" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/System+Procedures/default.aspx" /><category term="Deadlock" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Deadlock/default.aspx" /></entry><entry><title>SSMS Log file viewer and Deadlock Graphs</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/01/23/not-published-yet.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2008/01/23/not-published-yet.aspx</id><published>2008-01-23T16:02:00Z</published><updated>2008-01-23T16:02:00Z</updated><content type="html">Firstly I must say a big thank you to Microsoft for the new deadlock trace flag 1222. Compared to the trace flag output for 1204 &amp;amp; 1205 that you had to use in SQL 2000 it’s a walk in the park to interpret. Anyway, back to the post at hand! This is a quick FYI as i`m not going to go through how to interpret a deadlock graph because Bart Duncan does a fantastic job of it here . When you enable 1222, it will output the deadlock information to the error log. If your using the log file viewer and...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2008/01/23/not-published-yet.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=6341" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="Deadlock" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Deadlock/default.aspx" /></entry><entry><title>The Job whose owner kept coming back......</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2007/12/30/the-job-whose-owner-kept-coming-back.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2007/12/30/the-job-whose-owner-kept-coming-back.aspx</id><published>2007-12-30T19:25:00Z</published><updated>2007-12-30T19:25:00Z</updated><content type="html">I thought i would share this little quirk about the SQL Agent jobs for maintenance plans. One of our members of staff had left and we had the usual case of a few jobs failing with: "Unable to determine if the owner (DOMAIN\xxx) of job &amp;lt;JOB_Name&amp;gt; has server access (reason: error code 0x534. [SQLSTATE 42000] (Error 15404))." So, we went around and updated the job owners to one of our appropriate generic admin accounts. A few days later some of the jobs started to fail again with the same error...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2007/12/30/the-job-whose-owner-kept-coming-back.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=5888" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="Maintenance Plans" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Maintenance+Plans/default.aspx" /><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /></entry><entry><title>My old mate sp_recompile</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2007/10/12/My-old-mate-sp_5F00_recompile.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2007/10/12/My-old-mate-sp_5F00_recompile.aspx</id><published>2007-10-12T10:33:00Z</published><updated>2007-10-12T10:33:00Z</updated><content type="html">As soon as i saw the error messages in the logs i thought to myself "Oh my, that did not happen in testing" (ok, maybe it was more colourful than that).

We were creating a clustered index on a tiny little table and the index went through fine. However, the application started to generate the message "Could not complete cursor operation because the table schema changed after the cursor was declared". My gut reaction was to restart each application server in the cluster but having restarted the first one it made no difference. It suddenly clicked that SQL Server must be dishing out the cursor plan from cache.

Now, I did not want to restart the SQL servers because only a small part of the application was affected ...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2007/10/12/My-old-mate-sp_5F00_recompile.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=2651" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="SQL 2000" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2000/default.aspx" /><category term="Tips" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Tips/default.aspx" /><category term="System Procedures" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/System+Procedures/default.aspx" /></entry><entry><title>SSMS Restore backup error</title><link rel="alternate" type="text/html" href="http://sqlblogcasts.com/blogs/acalvett/archive/2007/09/14/ssms-restore-backups.aspx" /><id>http://sqlblogcasts.com/blogs/acalvett/archive/2007/09/14/ssms-restore-backups.aspx</id><published>2007-09-14T14:31:00Z</published><updated>2007-09-14T14:31:00Z</updated><content type="html">We had a requirement to allow someone to create and restore databases on a test server today and i thought to myself "Thats easy, i`ll just grant the "Create Any Database" right to the appropriate user, thats when the pain began!

The user was using SSMS connecting using a SQL login to restore a database and when they went to specify the backup location they got an error to the effect "Cannot access the specified path or file on the server". After clicking ok the tree view in the locate backup dialog was empty and if you typed in the path and filename manually you still recieved an error.

So, i dug out the profiler and found that xp_fixeddrives was being called and decided to check it out. It turns out that when executing xp_fixeddrives using a SQL login it returns no results! Because of this the error is generated in SSMS and the tree view is not populated.
...(&lt;a href="http://sqlblogcasts.com/blogs/acalvett/archive/2007/09/14/ssms-restore-backups.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://sqlblogcasts.com/aggbug.aspx?PostID=2519" width="1" height="1"&gt;</content><author><name>ACALVETT</name><uri>http://sqlblogcasts.com/members/ACALVETT.aspx</uri></author><category term="SQL 2005" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SQL+2005/default.aspx" /><category term="SSMS" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/SSMS/default.aspx" /><category term="Security" scheme="http://sqlblogcasts.com/blogs/acalvett/archive/tags/Security/default.aspx" /></entry></feed>