I discovered that problem was that although I had installed SQL2000 on the server I had not installed any service bug and there was a bug which was resolved by SP1. Once I installed the SP then I was able to resave the package using 2000 tools (and adding an owner password) and reschedule it...
Since installing a SQL2000 instance and client tools on my server I am having problems running a DTS package on the SQL7 instance. The package runs fine when from my PC, from the command prompt on the server or using xp_cmdshell in Query Analyser. The scheduled job does nothing and returns...
A user was getting an error 'login failed' it turned out that for the login she was using the 'default database' column was blank and this turned out to have been caused by the copy database wizard when it had detached this database temporarily when making a copy of it. Has anyone else ever...
I have had this problem where a server had somehow 'lost' its @@servername, but I found that running 'sp_addserver 'pro26', local' and restarting SQL server resolved the problem
Hi,
Your problem is that you are creating the database first before restoring it and you cannot restore directly from SQL7 to SQL2000. I assume you have got the SQL7 .bak file on the server somewhere, what you need to do is in Enterprise Manager, right click on databases, all tasks, restore...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.