Monday, March 19, 2012

Error copying databases in SQL Server 2005

How does one copy databases in SQLServer 2005?

I am trying to copy a database from one instance of SQLServer 2005 to another instance of SQLServer 2005 using the SQL Server Management Studio Copy Database Wizard. The source database is a continuously updatable database, while the destination database is used for reporting purposes.

When the wizard tries to create a SSIS package (as part of Copy Database), I get the following error:

While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80004005 ([DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.)

The details have additional message:
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.FolderExistsOnSqlServer(String strFolderName, String strServerName, String strServerUserName, String strServerPassword)
at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.EnsurePackageFolderExist(String folderName, Application app, String serverName, String loginName, String password)
at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()

=============================================

While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80004005 ([DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.)
-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.FolderExistsOnSQLServer(String bstrFolderName, String bstrServerName, String bstrServerUserName, String bstrServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.FolderExistsOnSqlServer(String strFolderName, String strServerName, String strServerUserName, String strServerPassword)

Hi

Copy database wizard is similar to EXPORT/IMPORT wizard of SQL Server 2000. There are new features in SQL Server 2005 for your scenario. You can use Database Mirroring, create a Snapshot on mirrored database for viewing data and can use for reporting services.|||Hi Jason,
This was a known problem in the past that should be working fine with the next CTP release. Right now, your best bet is to detach the database, copy to the destination, and then reattach it. You'll then need to copy recreate your logins at the destination to match with your users.
Thank you,
Bill Ramos

No comments:

Post a Comment