good question I think. Reminds people of the function (or brings it to their attention for the first time) so its educational, but steve put a little twist in it...

I would surmise 3MB was its default size.

Interesting, thanks for posting that back.

Just curious, if you did still use truncateonly (naughty 🙂 ), what did the file shrink to?

🙂

I would not expect it to give the error you see, but anyway the truncateonly option has no effect when applied to a log shrink

I have used this script...

I would not expect it to give the error you see, but anyway the truncateonly option has no effect when applied to a log shrink

that figure you remember of 10 databases on a 32bit server sounds like how many databases you can MIRROR on one server.

Even that is not a hard and fast...

definitely no.

SQL browser should be running when you have multiple instances

have you ticked the 'include updates' box?

There seem to be more sites out there that say the SMK gets created when it is needed to encrypt another key, including technet. However there are also some that...

thanks for posting that back.

One thing I forgot to mention it would now be worth defragmenting your indexes as the move about of the data is likely to have fragmented...

sorry, what? 🙂

note : 7 year old thread last posted to 3 and a half years ago - I highly recommend you post your question in a new thread (i.e add a...

just to be different, if the data is not changing, I would probably go for weekly. Why waste the resources (including tape) if the data is not changing?

If your failover site is for high availability or DR purposes and you don't require access to the failover database in normal circumstances I would never recommend replication as the...