And let us know what you find out!

One note for the R2 upgrade, I got a note from MS licensing. If you move from SQK2K8 (or 2005 I assume) with 16CPUs, to R2, you need to move...

Have you tried changing the growth to a set amount, say 30MB and seeing what that does? Then change it back to a %?

skjoldtc (4/28/2010)

---

I think Microsoft does admirable job with its SPs. It's a very complicated product and to chastise Microsoft for being "late" is short-sighted. I'd rather they release a correct...

jay holovacs (4/28/2010)

---

The analogy is not really accurate. Auto maintenance is to combat wear and deterioration, which inevitably occur.

Software does not wear, does not deteriorate. With the same inputs it...

Note that you...

I'd agree with Brandie that a good long Profiler session might help you identify what is using space.

Ugh

Sorry, hit enter too soon.

Can you open other packages? Can you open this package from another workstation (another SSMS instance)?

Typically I have seen this error when the server and client are at different levels, meaning one has been patched and one not. Or when someone has opened and saved...

Did you upgrade the server or client without the other? (Patch, SP, cu?)

Did the package get opened in BIDS or VS and saved back?

Don't hide, Adam, learn to manage. These people will be doing the SQL Server equivalent of "do you want fries with that" as you point them in the right direction.

There aren't relationships stored across databases. If someone has data related to something in another database, it's enforced outside of SQL Server.

The information views are a good place to start,...

Good luck finding something on the web if you can. If so, I'd be happy to help. I was thinking that maintaining a body of works (not published/visible) and submitting...

The Resource db is for the version of SQL Server, not the instance. You don't need to move it.