I don't necessarily think that you have to make friends at your job.  Heaven knows, there are a lot of people who, when they leave a company, never talk to...

Muhanned,

On the task that's giving you the error, try setting the DelayValidation property to True.  It might be giving you the error because it's trying to validate something (pre-package run)...

Yikes!  I totally missed the Exchange reference. (Good catch, Gail!)  That too could be a huge part of your problem.  I've never heard of anyone successfully having Exchange cohabitate with SQL Server...

Unfortunately, no.  It doesn't work that way.

Raid 1 config?  That might be your problem.  Raid 1 takes FOREVER to write to, double the time it would usually take to write...

Galanda,

Sounds like you're in the vague DBA/Developer realm.  If you maintain any sort of database, that qualifies you as a DBA, though maybe entry level if all you do is...

Rob,

Don't worry.  Profiler isn't a grenade. @=) You can't kill SQL by using it unless your system is so screwed up that it's hardly running at all and from what I...

Unfortunately, I can't leave the column out of the insert because I want to copy over non-default values from the database.  And since I have no control over other developers...

You don't have to take any class or buy any book.  Neither are actually cert exam pre-reqs as far as Microsoft is concerned.  Though they will eagerly sell you both (as will...

The problem with classes is they are VERY expensive and usually they try and get you to pass the test through ye old "Memorize it and then forget it" technique. ...

I have to admit, Joe's description is a pretty good one. @=)

To me, a senior DBA starts with a minimum of 1-2 years experience. 

I know some people don't like to say years of experience have anything to do with what a senior...

David,

Your schedule works great, for those of us whose only job duties are server upgrades. @=)

Though, I suppose if the products worked out of the box every time (or at least 99.9%...

Huh.  That's odd.  It's never done that to me before.  Though most of the time, when I'm going back and doing inserts, it's on tables created by the results of...

And if the other developers are sysadmin, you can run the Deny statement, but they can just undo it later on.

Easily solved, yes, but that doesn't explain why I got the error message in the first place.  All I did was a SELECT...INTO.  Nothing else except using that table in...