This is a very timely article/topic. I've worked for the same company for many years, and have always taken public transit to get to work. Up until 2...

paul.knibbs (12/8/2010)

---

I can see a potential issue here. You say users have lost data--but what if other users have updated the same database after that data loss? If you roll...

Should I apply SP3 for SQL Server 2005, before I try messing about with the maintenance plan modifications?

Thank you Gail, Lowell and Steve!

WOW, how timely this article is.

Ah, Craig, thank you. I need a mnemonic device to help me remember, and that will do.

WOW. Thank you. BTW, that control sequence isn't really obvious. (At least not to me.)

Actually in our environment, I noticed that we had 18 months worth of .bak and .trn files on the server. It was because of this that I thought I...

Craig Farrell (10/18/2010)

---

I... hesitate to tell YOU that it's okay to destroy YOUR backup files. However, I can help you figure out if it's right for you.

First, keep any...

upstart (10/18/2010)

---

Yes, you can safely delete these files. I would setup, if you do not have one already, a Job that will run periodically and auto-remove the old backups...

Thank you for the advise, GSquared.

Probably in most cases I can do that, but in some cases we have large wide columns (VARCHAR(4000) or so), and so I don't think I could do that in...

upstart (10/15/2010)

---

Changing the column type as you indicated should not produce any issues, so long as the data currently there fits into the new datatype.

Whenever you alter the structure of...

Interesting point, Steve. When it comes to public safety and/or health, one cannot be too careful.

BTW, loved the cat in your video of this post. 😉

I found that I had to set the IDENTITY_INSERT to ON, before I did the INSERT. Then I turned it back off again, which is the default.

To make it...