You can set the max memory for SQL under the server properties. If you don't set that, SQL will take as much memory as it can.

Duplicate post. No replies to this thread please.

Replies to:

http://www.sqlservercentral.com/Forums/Topic571604-145-1.aspx

Chirag (9/18/2008)

---

another way is to right click on the proc in SSMS and select view dependencies. It will show all objects that depend on the proc and also all...

Thanks James

That kind of comment is what makes it all worthwhile.

Have you looked in Books Online. There's a fair bit in there. Look under ALTER INDEX.

Check that the database you're running it in is in compatibility mode 90.

Duplicate post. No replies to this thread please

http://www.sqlservercentral.com/Forums/Topic571498-147-1.aspx

Please don't cross post. It just wastes people's time and fragments replies.

Answered here:

http://www.sqlservercentral.com/Forums/Topic570887-145-1.aspx

Then there must be something different about the databases that are on SQL 2000 and the databases that are on SQL 2005. The thing is, the error is saying there's...

I think you're going to have to restore it from a backup. SQL won't run properly without MSDB and, since it's a system database you can't just drop it.

I'd seen...

Stef (9/17/2008)

---

I'd like to hear how people would deal with this situation, if we replaced Index1 and 3 with a new Index with Column1, Column3, Column5 would that affect read...

http://msdn.microsoft.com/en-us/library/ms190749(SQL.90).aspx

SQL 2005 requires a password to be entered during installation if mixed mode is selected. It doesn't set a default. There's no practical way of decrypting the stored passwords

Sure. Add o.name to the select clause

You don't need to drop it before restoring, and I don't think it can be deleted.

Here's an msdn article on restoring MSDB

http://msdn.microsoft.com/en-us/library/ms190749(SQL.90).aspx

Before trying all that, try just running

RESTORE DATABASE...