SQL 2005 restoring backups files.....uncompessed?

A simple task I thought, restoring an old SQL 2000 database into my new SQL 2005 server.

I was getting this error;

Create failed for Database 'Compressed_DB'. (Microsoft.SqlServer.Smo)

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

The file "D:\Compressed_DB.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.

CREATE DATABASE failed. Some file names listed could not be created. Check related errors. (Microsoft SQL Server, Error: 5118)

I was completely stumped with the decompressed part of the message, found the solution though http://blogs.msdn.com/sanchan/archive/2006/06/04/617585.aspx .

- Simple fix is to restore the files back to my C drive which is uncompressed.
- Other fix would be to take compression off the offending d drive.

Understanding "login failed" (Error 18456) error messages in SQL Server 2005

More on vista on my development laptop.

SQL 2000 just doesn' run on vista. Bit of a pain, I have a virtual PC (XP SP2) running instead, but have installed SQL Server 2005, all went well, install did take ages.... But with installed I got the 'Understanding "login failed" (Error 18456) error messages in SQL Server 2005 ' error message which found this blog

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

All fixed now

EXECUTE permission denied on object 'sp_sdidebug', database 'master', owner 'dbo'.

I have hit a few problems after installing vista on to my laptop, the trickiest to fix was this one

EXECUTE permission denied on object 'sp_sdidebug', database 'master', owner 'dbo'.

When running Visual studio 2005 and debugging a site this error pops up, this is the easiest fix ever, thanks to Chris' blog; http://professionalaspnet.com/blogs/aspnet_blog/archive/2006/03/14/sp-sdidebug.aspx, it saved the day.

Simply put you have to set the debugger to only check the native code, otherwise it 'guesses' which code to debug including SQL code, which it doesn't have access right to.

More on the vista install as it happens

goodluck

EXECUTE permission denied on object 'sp_sdidebug', database 'master', owner 'dbo'.

I have hit a few problems after installing vista on to my laptop, the trickiest to fix was this one

EXECUTE permission denied on object 'sp_sdidebug', database 'master', owner 'dbo'.

When running Visual studio 2005 and debugging a site this error pops up, this is the easiest fix ever, thanks to Chris' blog; http://professionalaspnet.com/blogs/aspnet_blog/archive/2006/03/14/sp-sdidebug.aspx, it saved the day.

Simply put you have to set the debugger to only check the native code, otherwise it 'guesses' which code to debug including SQL code, which it doesn't have access right to.

More on the vista install as it happens

goodluck

firewall problems

With everyones pcs becoming 'robots' and more and more spam the question of what type of firewall you should use arises again and again, have a look at my gumtree posting - which firewall for some simple advice.

If you are stuck with what type of firewall you need, for home or business use please drop me an email support@chillfire.co.uk.

Google update complete causes chaos?

Check out my post http://www.v7n.com/forums/google-forum/46273-pagerank-vs-search-results.html#post535755

The V7n.com forums a re great place to get together with SEo people from all over the net, ask questions and even get answers.

SQL server MMC error

I got this a error when trying to open SQL enterprise manager;

AppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exe
ModVer: 5.1.2600.2180 Offset: 0001f07e

After some (much) searching I found this on http://www.sqljunkies.com/Forums/ShowPost.aspx?PostID=9302

-         It happens to be an error with the MMC application data file for enterprise manager in my user profile.

From windows explorer, browse to the "MMC" folder under C:\Documents and Settings\[user_profile]\Applicaiton Data\Microsoft\ (This is a hidden folder and to be able to view it you must show hidden files and folders in the "Tools" --> "Folder Options" --> "View" settings). There should be a file named "SQL Server Enterprise Manager". You can either delete or rename this file (I prefer the latter). MMC will re-create this file the next time you access Enterprise Manager and should then be working properly.

Fixed the problem