Showing posts with label moving. Show all posts
Showing posts with label moving. Show all posts

Monday, March 12, 2012

Question on moving packages to another server

I am trying to move a package to another server, the package is on the file system and I made certain that the folders are the same and the paths match.

However when executing on the other server I get an error 0xC0012050 whil loadin package file...package failed validation from the Execute Package task. The package cannot run.

The path in the error is correct and the package name is correct.

This is one package executing 2 other packages.

Also then when it tried to run the package I received the "package cannot run" error - I received the ODBC error 08001 error during OPENP in DBOpen ERROR [08001] PLAN ALREADY EXISTS.

Am I getting the second error because I received the first error that the Package cannot run?

How do I determine why the package cannot run on the other server?

MaryOS wrote:

Am I getting the second error because I received the first error that the Package cannot run?

How do I determine why the package cannot run on the other server?

It may be the other way around; a problem with one of the connections may be causing the validation to fail. I don't know about that specific error; but make sure all the connection managers are valid.

Question on moving logs

Running SQL Server 2000. I have been asked to move the transaction logs
to another drive. I was able to do that for the user databases using
detach/attach.

However I don't see that as an option for moving the logs for the
system databases.
Is there any way I can move the system database logs? I'm guessing it
might be possible through a restore.

Any thoughts ?

Thanks in advance.

GerryShutdown the service, and change thew appropiate registry settings for
the temp and the master database. The other databases can be moved with
attach / detach.

HTH, Jens K. Suessmeyer.

--
http://www.sqlserver2005.de
--|||Jens wrote:

Quote:

Originally Posted by

Shutdown the service, and change thew appropiate registry settings for
the temp and the master database. The other databases can be moved with
attach / detach.
>
HTH, Jens K. Suessmeyer.
>
--
http://www.sqlserver2005.de
--


Thanks Jens

Also came across this

http://support.microsoft.com/kb/224071/

Question on moving logs

Running SQL Server 2000. I have been asked to move the transaction logs to another drive. I was able to do that for the user databases using detach/attach.

However I don't see that as an option for moving the logs for the system databases.
Is there any way I can move the system database logs? I'm guessing it might be possible through a restore.

Any thoughts ?

Thanks in advance.

GerryGiven the number of transactions that happen in master, model and msdb on a daily basis, I have never found it necessary to move the logs of these three databases. Tempdb on the other hand can be moved with a dirty trick. Leave the existing log with a maxsize limit of say 5MB, and create a second logfile on the new device at the actual size you need. Logfiles are used in sequence, as opposed to datafiles which are used in a more distributed way. You will still have the original disk used for 5MB of logs every once in a while, but the vast majority of the usage should be on the other drive.|||Thanks

Also came across this article

http://support.microsoft.com/kb/224071/