| Author |
Topic |
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
 Posted - 2002-11-13 : 09:57:02
|
| Some SQL 2K servers have been introduced to our network and I was required to install the 2K tools on my desktop to monitor those servers as well as our production SQL 7 servers.Now, whenever I open EM or QA it is the 2K version of the tool. I fear I'm going to have problems with modifing SQL 7 DTS pkgs (for example) ...How do you run 7 and 2K tools at the same time?EDIT: After reading a bit more searching it seems that the 2k tools replace the 7 tools on the same box. How does that effect DTS? Are there any 2K features exposed in the DTS package designer that will not work with SQL 7? Jay White{0}Edited by - Page47 on 11/13/2002 10:48:05 |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-11-13 : 11:07:02
|
| I have been working with the same environment for the past couple of months and have not yet has any issues. I have written a handful of DTS package in the designer to do various things, and they have all scheudled and run fine from both 2K and 7.0 servers. I'm sure there are DTS features that are not available on 7.0, but I haven't run into them yet. EM seems to adjust screens and tools accordingly depending on the version of the server you are connected to. I am running SQL2K SP2 on my client and SP2 with the security Hotfix on all 2K servers. I am runnning SP4 on all 7.0 servers. HTH.Jeff BanschbachConsultant, MCDBA |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-11-13 : 12:17:26
|
| If you save a dts package using the 2000 client then try to run it on a m/c with onlky the v7 client you will get and invalid property error for all the sql server connections.I think the property that 2000 adds is The only way to get rid of this is to open the package with a v7 client open each connection, connection, properties, advanced, ok, ok, no (important or you will lose all the transformations) then save the package.If you are not getting errors it probably means the 2000 dts dlls are on the machine that the packages are being run from.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-11-13 : 12:26:04
|
| I thought they fixed that problem with SQL2K SP2... I am not experiencing it on my SQL7 servers and I know they have never had any SQL2K components loaded.Jeff BanschbachConsultant, MCDBA |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-11-13 : 12:59:32
|
| A new feature to DTS in SQL 2K is the "Execute Package Task" ...What happens if I create a DTS package that uses that on a client box with SQL 2Ksp2 and execute it on a SQL 7sp3 server?My initial testing shows that it works? But the SQL 7 Server should know nothing about Execute Package Task ... I don't get it ...Jay White{0} |
|
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-11-13 : 13:59:24
|
quote:
My initial testing shows that it works? But the SQL 7 Server should know nothing about Execute Package Task ... I don't get it ...
Are you running your DTS package from the server or from your own workstation? If you are running it from the personal workstation, it will work fine -- your workstation has SQL2k components and knows all about Execute Package Task. It doesn't matter that the package is saved on the server, as long as it is run by your machine. However, if you run it from the job on your SQL7 box (or run it using SQL7's EM from some other machine), I'm pretty sure the package will error out.Edited by - izaltsman on 11/13/2002 14:01:39 |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-11-13 : 14:11:55
|
quote:
...I'm pretty sure the package will error out....
Right, so that's exactly my point....My production servers do not know anything about SQL2K .... my desktop has the 2K tools. All my prod DTS pkgs are scheduled as jobs and run overnight. If I edit a prod pkg from my desktop, will it work tonight? (I'm not going to try just yet)My aforementioned initial testing was in error. My desktop is also running a SQL 7 server. I used the 2K tools to create a 2K pkg on my desktop (this package used an Execute Package Task to call another package). I ran the package against my desktop from the 2K tools (EM) on my desktop ... It worked (as expected) ... I then schedule the pkg as a job ... I figured this should run it under the context of SQL 7 and it should fail since SQL 7 doesn't know about EPT ... but it worked too ... But now I wonder what would happen if I move that pkg to a 7 machine that doesn't have 2K tools? Did the 2K client tool install change my desktops 7 server? Maybe ...Jay White{0} |
|
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-11-13 : 15:17:23
|
quote:
But now I wonder what would happen if I move that pkg to a 7 machine that doesn't have 2K tools? Did the 2K client tool install change my desktops 7 server? Maybe ...
Installing SQL2k tools didn't change your SQL7 server, but it did give you the dll's you need in order to execute new tasks in your DTS packages. But, like you said, if you try to execute your package from the machine that does not have SQL2k tools, it will not work. As to whether your production packages will work if you edit them from your desktop -- I am almost positive that they will work just fine, as long as you don't try to add features that aren't available on SQL7... I don't recall having any problems back when I had to manage SQL7 servers with SQL2k tools here, but of course you are better off testing it out for yourself. |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-11-14 : 04:28:28
|
| dts is an external application - it is executed on the client not the server (although they may be the same).It doesn't matter what the server is.It's the machine on which dts is being run that's important.If you create a dts package on a 2000 client then try to run on a v7 client it will get the error that I gave above.If you run as a job on a v7 server or load it using a client oin that server you will also get the error.If the v2000 client (or just the 2000 dts dll's) have been loaded on that server or you load the package on a 2000 machine and connect to the v7 server then it should be OK.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy.Edited by - nr on 11/14/2002 04:29:31 |
|
|
|
|
7 and 2k client tools on same machine