Copy Database from SQL 2000 to SQL 2005

Howdy,
I'm trying to use the Copy Database wizard in SQL Server Management Studio
to copy a database from a SQL 2000 Server to my local SQL 2005 Express.
After running the wizard it errors out with the following. I can connect to
the 2000 server fine using the management studio as well. Any ideas?
StackTrace: at
Microsoft.SqlServer.Management.Common.ConnectionMa nager.Connect()
at
Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask. TransferObjectsTask.OpenConnection(Server&
server, ServerProperty serverProp)
InnerException-->An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused
by the fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not open a
connection to SQL Server)
StackTrace: at
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException exception,
Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject)
at
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SqlServer.Management.Common.ConnectionMa nager.InternalConnect(WindowsIdentity
impersonatedIdentity)
at Microsoft.SqlServer.Management.Common.ConnectionMa nager.Connect()
On Mar 6, 12:21 pm, "David Lozzi" <dlo...@.nospam.nospam> wrote:
> Howdy,
> I'm trying to use the Copy Database wizard in SQL Server Management Studio
> to copy a database from a SQL 2000 Server to my local SQL 2005 Express.
> After running the wizard it errors out with the following. I can connect to
> the 2000 server fine using the management studio as well. Any ideas?
> StackTrace: at
> Microsoft.SqlServer.Management.Common.ConnectionMa nager.Connect()
> at
> Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask. TransferObjectsTask.OpenConnection(Server&
> server, ServerProperty serverProp)
> InnerException-->An error has occurred while establishing a connection to
> the server. When connecting to SQL Server 2005, this failure may be caused
> by the fact that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not open a
> connection to SQL Server)
> StackTrace: at
> System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException exception,
> Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
> stateObj)
> at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
> SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
> timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
> integratedSecurity, SqlConnection owningObject)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo
> serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
> timerExpire, SqlConnection owningObject)
> at System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String
> host, String newPassword, Boolean redirectedUserInstance, SqlConnection
> owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
> owningObject, SqlConnectionString connectionOptions, String newPassword,
> Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity
> identity, SqlConnectionString connectionOptions, Object providerInfo, String
> newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection
> owningConnection, DbConnectionPool pool, DbConnectionOptions options)
> at System.Data.ProviderBase.DbConnectionPool.CreateOb ject(DbConnection
> owningObject)
> at
> System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
> owningObject)
> at System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
> owningObject)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SqlServer.Management.Common.ConnectionMa nager.InternalConnect(WindowsIdentity
> impersonatedIdentity)
> at Microsoft.SqlServer.Management.Common.ConnectionMa nager.Connect()
Complaints about the "Copy Database" wizard are common in this group,
and the response is always the same - don't use it. It's much faster
and easier to do a simple backup/restore of the database. The copy
wizard is flaky and throws up a variety of bizarre issues, depending
on what day of the week it is...
|||Not for nothing but its not easier to backup/restore when i'm sucking it
down from a web server... can i get this to work?
Thanks,
David Lozzi
"Tracy McKibben" <tracy.mckibben@.gmail.com> wrote in message
news:1173206717.382194.282980@.t69g2000cwt.googlegr oups.com...
> On Mar 6, 12:21 pm, "David Lozzi" <dlo...@.nospam.nospam> wrote:
> Complaints about the "Copy Database" wizard are common in this group,
> and the response is always the same - don't use it. It's much faster
> and easier to do a simple backup/restore of the database. The copy
> wizard is flaky and throws up a variety of bizarre issues, depending
> on what day of the week it is...
>