|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Use Management Studio with 2000 databases?I just installed SQL Server 2005 Development Edition and I really like
Management Studio as compared to Enterprise Manager. Is there any reason why I should NOT use Management Studio to work with my existing SQL Server 2000 databases? None that I have found.
-- Show quoteArnie Rowland Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous "jmelkerson" <jmelker***@discussions.microsoft.com> wrote in message news:0C7709B4-0BB5-4228-ACAC-C39793D613C4@microsoft.com... >I just installed SQL Server 2005 Development Edition and I really like > Management Studio as compared to Enterprise Manager. Is there any reason > why > I should NOT use Management Studio to work with my existing SQL Server > 2000 > databases? One minor issue: you might need to download the Microsoft SQL Server 2000
DTS Designer Components http://www.microsoft.com/downloads/details.aspx?familyid=DF0BA5AA-B4BD-4705-AA0A-B477BA72A9CB&displaylang=en Other than that, I have been connecting to SQL Server 2000 databases via SQL Server Management Studio without any issue. -- Show quoteKeith Kratochvil "jmelkerson" <jmelker***@discussions.microsoft.com> wrote in message news:0C7709B4-0BB5-4228-ACAC-C39793D613C4@microsoft.com... >I just installed SQL Server 2005 Development Edition and I really like > Management Studio as compared to Enterprise Manager. Is there any reason > why > I should NOT use Management Studio to work with my existing SQL Server > 2000 > databases? On Fri, 21 Jul 2006 10:59:02 -0700, jmelkerson
<jmelker***@discussions.microsoft.com> wrote: >I just installed SQL Server 2005 Development Edition and I really like During the CTPs there were issues when installing SQL Server 2000>Management Studio as compared to Enterprise Manager. Is there any reason why >I should NOT use Management Studio to work with my existing SQL Server 2000 >databases? Enterprise Manager on a machine with SQL Server Management Studio (or vice versa) - parts of Enterprise Manager wouldn't work. From your description that is hopefully a potential problem you won't encounter. Andrew Watt MVP I would like to point out that you should probably install the SQL Server
Management Studio (SSMS) along side Enterprise Manager (EM) if you use the following features. - Database Diagrams. In SSMS, you can only design against SQL 2005 server databases. You'll need EM for working with SQL 2000 server databases. - Maintenance plans. You have greater control over the scheduling of Maint Plans with SQL 2000 than with SSMS going against SQL 2000. Service Pack 2 will address many of these concerns. Just about everything else works as expected using SSMS against SQL 2000. There are lots of minor things that SSMS took away - many will be fixed in SP2 as well. Thank you, Bill Ramos, Lead PM, SQL Server Manageability This posting is provided "AS IS" with no warranties, and confers no rights Show quote "jmelkerson" <jmelker***@discussions.microsoft.com> wrote in message news:0C7709B4-0BB5-4228-ACAC-C39793D613C4@microsoft.com... >I just installed SQL Server 2005 Development Edition and I really like > Management Studio as compared to Enterprise Manager. Is there any reason > why > I should NOT use Management Studio to work with my existing SQL Server > 2000 > databases? |
|||||||||||||||||||||||