 | |
SQL 2000 Enterprise Manager on Win 7
microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: SQL 2000 Enterprise Manager on Win 7 -
09-04-2009
, 12:52 PM
|
If we cannot use SQL2008 Client tools on Windows 7 what other functions might fail because we are still on SQL2005 SP2? Why cant you use 2008 client tools on Windows 7? Why can't you apply SP3 to your 2005 client tools on Windows 7? I don't know of all the functions that will fail if you insist on staying at SP2. I just simply wouldn't do it. There were plenty of fixes to maintenance plans after SP2, for example. So if you use those, you are using them at your own risk. Obviously you don't get any of the feature enhancements in 2008; I don't think there were any feature changes between SP2 and the current builds of the 2005 version. If you want a full category of "things that might go wrong if I decide to do it this way" you will probably have to comb the individual fixes in post-SP2 CUs, SP3, and post-SP3 Cus to find the ones that affect the tools, and deem if they affect you. I don't keep such a list off the top of my head because I see no reason to stay on an antiquated version of the client tools... |
#12
| |||
| |||
|
|
I think it should be client version should be >= server, not client version must = server. The situation that scares me is when client < server. So, as you can, upgrade clients. It doesn't have to be all or nothing, but you may want to focus on the users who do "more advanced" stuff using the UI, because that is typically the stuff where fixes are important. On 9/4/09 1:52 PM, in article uJGp2hYLKHA.4376 (AT) TK2MSFTNGP03 (DOT) phx.gbl, "Chris Wood" <anonymous (AT) microsoft (DOT) com> wrote: Aaron, We like to keep our Client tools on the desktop to the same level as the server. As a government department with lots of maintenance work going on it is difficult to add in the wholesale upgrades that are needed and now money is getting short. Thanks Chris "Aaron Bertrand" <moc.liamg (AT) dnartreb (DOT) noraa> wrote in message news:C6C6C94C.23BF4%moc.liamg (AT) dnartreb (DOT) noraa... If we cannot use SQL2008 Client tools on Windows 7 what other functions might fail because we are still on SQL2005 SP2? Why cant you use 2008 client tools on Windows 7? Why can't you apply SP3 to your 2005 client tools on Windows 7? I don't know of all the functions that will fail if you insist on staying at SP2. I just simply wouldn't do it. There were plenty of fixes to maintenance plans after SP2, for example. So if you use those, you are using them at your own risk. Obviously you don't get any of the feature enhancements in 2008; I don't think there were any feature changes between SP2 and the current builds of the 2005 version. If you want a full category of "things that might go wrong if I decide to do it this way" you will probably have to comb the individual fixes in post-SP2 CUs, SP3, and post-SP3 Cus to find the ones that affect the tools, and deem if they affect you. I don't keep such a list off the top of my head because I see no reason to stay on an antiquated version of the client tools... |
#13
| |||
| |||
|
|
Use 2008 Management Studio. Run a query in grid mode. Click the top left corner so the entire grid is selected, right-click the top left left corner, and choose "Copy with Headers"... Then paste into Excel. Voila! Kiss your 10-year old tool goodbye. |
and check "Include column headers when copying or saving results".
With this options you get it everytime you copy from the grid, save
when copying values from a single column.
Slightly easier to use - but you may also get column headers when you don't
want them.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx
#14
| |||
| |||
|
|
Based on your comments, when we go Windows 7 we should have SQL2008 Client tools even though we will most probably be running SQL2005 SP2 and SP3 builds. Thanks Chris "Aaron Bertrand" <moc.liamg (AT) dnartreb (DOT) noraa> wrote in message news:C6C6CFE6.23C07%moc.liamg (AT) dnartreb (DOT) noraa... I think it should be client version should be >= server, not client version must = server. The situation that scares me is when client < server. So, as you can, upgrade clients. It doesn't have to be all or nothing, but you may want to focus on the users who do "more advanced" stuff using the UI, because that is typically the stuff where fixes are important. On 9/4/09 1:52 PM, in article uJGp2hYLKHA.4376 (AT) TK2MSFTNGP03 (DOT) phx.gbl, "Chris Wood" <anonymous (AT) microsoft (DOT) com> wrote: Aaron, We like to keep our Client tools on the desktop to the same level as the server. As a government department with lots of maintenance work going on it is difficult to add in the wholesale upgrades that are needed and now money is getting short. Thanks Chris "Aaron Bertrand" <moc.liamg (AT) dnartreb (DOT) noraa> wrote in message news:C6C6C94C.23BF4%moc.liamg (AT) dnartreb (DOT) noraa... If we cannot use SQL2008 Client tools on Windows 7 what other functions might fail because we are still on SQL2005 SP2? Why cant you use 2008 client tools on Windows 7? Why can't you apply SP3 to your 2005 client tools on Windows 7? I don't know of all the functions that will fail if you insist on staying at SP2. I just simply wouldn't do it. There were plenty of fixes to maintenance plans after SP2, for example. So if you use those, you are using them at your own risk. Obviously you don't get any of the feature enhancements in 2008; I don't think there were any feature changes between SP2 and the current builds of the 2005 version. If you want a full category of "things that might go wrong if I decide to do it this way" you will probably have to comb the individual fixes in post-SP2 CUs, SP3, and post-SP3 Cus to find the ones that affect the tools, and deem if they affect you. I don't keep such a list off the top of my head because I see no reason to stay on an antiquated version of the client tools... |
#15
| |||
| |||
|
|
Actually, I would recommend having both the 2008 and 2005 tools, patched to the latest SP at least. Without the 2005 tools, you won't have 2005 BIDS - and creating reports and SSIS packages in 2008 is not backward compatible with 2005 deployments. |
Quote:
|
There is nothing wrong with having both sets of tools on a system. |
#16
| |||
| |||
|
|
Actually, I would recommend having both the 2008 and 2005 tools, patched to the latest SP at least. Without the 2005 tools, you won't have 2005 BIDS - and creating reports and SSIS packages in 2008 is not backward compatible with 2005 deployments. Well, that's if he needs BIDS / SSIS etc. There is nothing wrong with having both sets of tools on a system. There is if you don't install them in the right order! |
#17
| |||
| |||
|
|
What would be the right order? SQL2005 first followed by SQL2008 or the other way round? Chris "Aaron Bertrand" <moc.liamg (AT) dnartreb (DOT) noraa> wrote in message news:C6C74B9C.357B5%moc.liamg (AT) dnartreb (DOT) noraa... Actually, I would recommend having both the 2008 and 2005 tools, patched to the latest SP at least. Without the 2005 tools, you won't have 2005 BIDS - and creating reports and SSIS packages in 2008 is not backward compatible with 2005 deployments. Well, that's if he needs BIDS / SSIS etc. There is nothing wrong with having both sets of tools on a system. There is if you don't install them in the right order! |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.