When SQL Server 2k5 declares war on your common sense
I've been having more and more SQL 2k5 oddities as the weeks go by, and haven't been able to solve most of them yet. I never had half these issues with 2000, not really sure why not.
- If you need to turn on C2 trace auditing, or run a custom trace I've found I can no longer use the gui to take databases offline and bring them back up. They go offline just fine, but when you select to bring them online I am always returned with an error. It reads something like HI! I cannot bring this online because I cannot set its mode to offline since it is offline.... uhh what?
- If I have replication running on a particular table, I can no longer do a bevy of various tasks to the table like taking it offline or detaching it via the gui. I also cannot modify the schema or make minor tweaks to it, even outside of the replication window these are not allowed because of active subscriptions it says. Well, not allowed from the gui anyhow. I can issue t-sql commands to do the modifications just fine, and it never seems to affect replication negatively.
- No matter which user I set to own a job, it tends to put whomever I am logged in as under the job owner. It doesn't always seem to do this, and I can't honestly figure out why. When locking things down by user, this one really sucks and drives me crazy. The tasks end up not running, sometimes switching the owner under the specific jobs doesn't resolve it, but logging in as the user you want and re-creating the job does the trick. Its very frustrating.
I'm sure the bulk is from my inexperience as a faux DBA, but I never seemed to run into these quirks and so many others on 2000, only on 2005.




There are no comments for this entry.
[Add Comment]