I see something "similar" with our database maintenance plans when we remove a database. For some reason, it doesn't automatically get omitted from the backup plan (which has all...

any ideas anyone? thanks,

what edition of 2008 are you on? Have you looked into compression?

http://blogs.msdn.com/b/sqlserverstorageengine/archive/2007/11/12/types-of-data-compression-in-sql-server-2008.aspx

http://technet.microsoft.com/en-us/library/bb964719.aspx

Andrew

I was lucky that I'd had a similar problem querying sys.partitions recently, and received an error due to the collation of the database (I had used a capital 'P' for...

SQLkiwi (9/8/2011)

---

Tom.Thomson (9/8/2011)

---

Good question and answer.

But the behaviour still seems bizarre to me. Why should the loop join hint be taken to imply the (Force Order) option - if...

It looks as though you should be okay.

msdb.dbo.backupset has a foreign key constraint on backup_set_id with msdb.dbo.backupfilegroup, so as long as you restore the associated rows, I can't...

I inserted the contents of old_msdb.dbo.restorehistory into msdb.dbo.restorehistory without any problems. Do you have a particular table in mind you want to recover? I don't mind breaking my...

Hi,

I've just restored a backup of msdb to 'old_msdb' on one of our virtual servers. It went into the user database list no problem

Andrew

OK. Thanks for your help

Pure guess work from me...

Hi,

I'm working with Adam on this upgrade.

When it comes to Windows Server Roles (we'll have Win2K8 R2 EE), what role should be picked for SQL Server? No Analysis Services...

Hi,

This script is great - thanks. One small problem I've found, if the database collation uses a binary sort, I get an error stating that <databasename>.dbo.sys.Partitions could not be...

The exams are to test YOUR knowledge of SQL Server, not someone elses. A quick google search of '70-432' will give you a long list of reading material, but...

Are you working directly on the server that you're trying to remove log shipping from? If so, do you have the SQL server registered as <local>, etc. rather than...

Have you checked the SQL Service account?