March 14, 2007 at 2:06 pm
We're finally biting the bullet and migrating to SQL Server 2005... so now instead of poking around with Management Studio, I get to start using it full time.
I've been using SQL Server 2000 for a bit over five years now, and I like to think I'm a power user. I script everything I can, can get useful information out of SQL Profiler with minimul fuss, have a dozen or so Query Analyzer templates that I practically live by, know the keyboard shortcuts for most everything (saved at least a week of tedious frustration time with the Ctrl+B shortcut in Query Analyzer alone), can prove that it's not the database server that's causing the Production problem in mere minutes... in short, I'm a Database Administrator who can readily get the job done with the basic tools provided.
In 2005, they change everything. I just spent 30+ minutes finding where they store the (no longer called) Query Anaylzer templates, and Shift+Ctrl+Insert doesn't pop them up any more, so I have to waste time positioning the mouse just so, and don't start me on my dearly departed and sorely missed Ctrl+B...
Whine whine whine. My question is this: About how long can I expect it to take me to become accustomed to Management Studio? To get familiar with how it works? To stop using all my old reflexes, learn the new shortcuts, and start using them?
How big is the adoption curve for actually using SQL Server 2005?
Philip
(Looking forward to when I can start using the new 2005 features, tools, and tricks... but I gotta be able to support our existing infrastructure first.)
March 14, 2007 at 3:20 pm
Wow, you think you are on a huge learning curve now? And you are just dealing with Management Studio.... Wait til you start with SSIS - that is LOADS of fun. In Management Studio system databases have moved to their own 'folder'. There is now SQL Server Error Logs and SQL Server Agent Error Logs. A lot of stuff has moved, it's a pain to learn where to find things now. Some system tables have changed (I don't know which ones off the top of my head, but I've run into problems with them). Some system tables have to be prefixed with sys instead of dbo.
Good luck...I'm still trying to learn SQL Server 2005 and I started with it in September 2006.
-SQLBill
March 14, 2007 at 4:01 pm
Our other DBA gets to tackle SSIS. I figure the more I do of everything else, the better the chance he has of getting them usable. (We're not converting, we're using the legacy DTS package support, but even so.)
We've got a test environment in place. I just stumbled over the fact that, on upgrading, the domain security policy gets applied to all SQL logins... so in 60 days, the passwords would unexpectedly expire. Yoiks! How many other Easter Eggs like this am I going to find? (Easter Eggs are fine, unless you find them 60 days after they were hidden...)
Philip
March 14, 2007 at 5:20 pm
Wow, we haven't come across that one (SQL logins falling under the domain security policy).
You're going to find out that DTS and SQL Server 2005 don't play well with each other. You will need to download the 2005 Feature Pack DTS fix.
-SQLBill
March 15, 2007 at 8:11 am
Forget Query Analyser. You can admin your 2000 servers from Management Service and far better. See that button that says "script this"? ANYTHING you do - press that button - it will give you the script. ANY bit of ad hoc code you write - it will offer to save in a hierarchy.
And NO MORE MODAL WINDOWS !
Roger L Reid
March 15, 2007 at 9:11 am
once you start using it, it will come to you after a while. some things are better than SQLEM and QA others are annoying.
only think i can say is with your upgrade go slow, since there are still bugs in there. Do a distributor, one publisher and a subcsriber and let it run for a few weeks.
so far every problem we have would not have been caught in testing because they are pretty obscure.
March 15, 2007 at 1:25 pm
I have found it very frustrating. Attempting to use MGT studio to grant select access to 50 tables to one user... good luck... you have to do every table seperately. It took me 30 minutes to even find how to do it....
Some of the reports do not work, you have to right click and say create to Excel.... jeesh...
MGT studio is sooo slow to load and do some things...
However, there are some good things. Some of the reports ARE very good, the refresh feature for say Current Activity is finally a simple click AND you can auto refresh every X seconds... Great !
Another awesome feature is the history of table changes... you add a column or change an index and you have the history of when and what ID made the change.
We have one very small SQL 2005 install right now that has so low of activity I cannot really play with the tools much.
March 15, 2007 at 1:35 pm
We are starting a Data Warehouse project, and will be using SQL Server 2005, SSIS, SSRS, and hopefully SSAS. we are also using WSS v3 (x64) to support our development team. May also use WSS to help front end the warehouse/marts when we go production.
I have been playing with (getting to know SQL Server 2005) since early 2006. I purchased SQL Server 2005 Developer Edition to load on my computer at home. It was one of the best $50 investments I have made.
Only thing I still don't like about SSMS is I can't debug stored procedures I write. To do that I will need to get Visual Studio 2005 Professional (Standard isn't good enough). My thought is, if you can write it in SSMS, you should be able to debug it in SSMS. Hope they change that in SP3.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply