GilaMonster (10/13/2011)

---

Yes, the index rebuild is causing your log to grow. It will.

Truncate and Shrink is a very, very bad thing to be doing regularly to the log, it's...

what recovery mode is your database in?

this trip into space, is it one way or return?

http://msdn.microsoft.com/en-us/library/ms191233.aspx

the last log you restore you should use the with recovery option to bring the database online.

anything grabbing the memory before SQL starts up?

please don't duplicate post about duplicate posts. It just wastes space on the database

😀

on one of the VMS yes, multiple installs across the host, probably not, you would have to check with whoever you bought the licenses off.

BenWard (10/11/2011)

---

thanks.

as for union all, it makes no odds for the purpose of this example or if you're trying to...

nice to see this type of question rather than all those coding ones!

nice question, strictly speaking shouldn't it be union all?

I think it is a security issue, not allowing users to execute other peoples jobs and thus granting them access they should not have.

I dare say the devs would prefer...

#1 I would provide them a script\stored proc to create all databases which includes the permissions.

#3 The ONLY way to accomplish this (short of granting sysadmin) is to create a...

Do you have a new SQL2008 server built?

If so backup\restore is usually best, the copy wizard would be my last choice.

is the rollback completion increasing?

Is this backup executed via a third party tool?

Ok kevin, I will probably be the first of many......

its the reindex that is causing the log growth. Thats normal behaviour.

remove the truncate log and shrink, totally pointless and in...