Showing posts with label 2005 Bugs. Show all posts
Showing posts with label 2005 Bugs. Show all posts

Tuesday, February 02, 2010

Interesting Bug with dbcreator role

With a user with dbcreator role when you try to backup or restore the database using GUI you will get the below error.

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup
Cannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists.

If you know that the service account can access a specific file, type in the full path for the file in the File Name control in the Locate dialog box.



Looks like a bug as specified here . The work around is also provided there which is to restore using scripts.

Monday, May 28, 2007

Beware while creating Maintenance plans using SP2.

I created maintenance plans from my laptop which has got SP2 to the servers that doesnt have SP2 installed. I observed that the old backup files didnt get deleted, I was wondering if that is a bug too so I started to create the maintenance plans from the server itself. so guys beware of this fact. I dont even know if that is a bug or not. Need to verify the same in other servers.

The another glitch is when you create a maintenance plan using a machine with SP2 we cant edit it from a non sp2 client or server, this is the way SP2 has been designed to work so guys beware of this fact too.

Any thoughts or insights in this? Did some one else found out similar issues?

Sunday, March 18, 2007

log_reuse_wait_desc

Last week I got a production call on transaction log full. hmmm there was no chance for that database log to get filled. I was wondering and when I looked into the database it said the transaction log is waiting for the replication to complete. I was like whatttttttttttt, since I had a replication build earlier and dropped it as it didnt work out good.

Then after doing some research I found out like there is a bug with the SQL 2005 in which even if we remove the replication, it doesnt remove it clearly. This issue was discovered in CTM and we are currently in SP1, the issue exists till now. It is being discussed in this MSDN form . It was really too scary ouchhhhhhhh.