Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
julesr
Starting Member
14 Posts |
Posted - 2003-11-29 : 19:29:41
|
| I'm working on a website and for the most part everything is OK. The SysAdmin has given me a username/password to connect to the SQL server on their dedicated server. They have also given me a CiscoSystems VPN Client that I need to start up before connecting to their server.Now, the problem arises when I create a DTS package. When I create it, the owner is LAPTOP/JulianRoberts. Which is my local machinename/username. I can manually execute the steps (by right-clicking) and it all works fine. But, when I try and schedule the package to run every morning, it falls over.SysAdmin informs me that my package cannot be scheduled because of permission problems. What SysAdmin then did was to create a new package which was basically a copy of mine. This now runs great.But, the problem now is that I can't edit the package that SysAdmin created. At the moment, I have to make changes to the package that I created and then sysAdmin has to copy the changes over to the package he created.This doesn't strike me as quite right. Is there something that SysAdmin can do to make our lives easier?Juleshttp://www.charon.co.uk |
|
|
|
|
|