hi,
I have a sql box under diff domain. I login as sqladmin mapped a network
drive pointed to the dir that I need to copy the files.
I created a job under command prompt--copy /Y z:\*'* \\server2\myfoleder\
If I run it under ms dos --OK, but running it through sql server job, got
this error:
The system cannot find the drive specified.
Any ideas
ThanksdOk, it is all a matter of security contexts:
WHO are you when you run from the command line?
WHO are you when you run a SQL Server Job:
If job runs as system administrator?
If job runs as a non-system administrator?
Does whatever account is actually running the job actually have rights to
the drive? Apparently not.
Also, FWIW, it is usually better not to use drive letters. Make a share and
use it with the standard non-dos notation.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:%23THGzfPTGHA.4752@.TK2MSFTNGP10.phx.gbl...
> hi,
> I have a sql box under diff domain. I login as sqladmin mapped a network
> drive pointed to the dir that I need to copy the files.
> I created a job under command prompt--copy /Y z:\*'* \\server2\myfoleder\
> If I run it under ms dos --OK, but running it through sql server job,
> got this error:
> The system cannot find the drive specified.
>
> Any ideas
> Thanksd
>
Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts
Tuesday, March 27, 2012
copy files
Hi,
I have two servers within the same domain. Using CMD Prompt, when I copy
files from one server to another, it works flawlessly, eg. COPY
D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
However, when I use the same command in a CMDEXEC step of a job, it gives me
an Access Denied error message.
Any help. Thanks in advance for all your help.Make sure that the account that the SQL Server Agent runs in has permissions
on the source/ destination. Thats the account that jobs run in.
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:3FED8D10-A43F-431A-94EF-0F51271B5E82@.microsoft.com...
> Hi,
> I have two servers within the same domain. Using CMD Prompt, when I copy
> files from one server to another, it works flawlessly, eg. COPY
> D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
> However, when I use the same command in a CMDEXEC step of a job, it gives
me
> an Access Denied error message.
> Any help. Thanks in advance for all your help.
I have two servers within the same domain. Using CMD Prompt, when I copy
files from one server to another, it works flawlessly, eg. COPY
D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
However, when I use the same command in a CMDEXEC step of a job, it gives me
an Access Denied error message.
Any help. Thanks in advance for all your help.Make sure that the account that the SQL Server Agent runs in has permissions
on the source/ destination. Thats the account that jobs run in.
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:3FED8D10-A43F-431A-94EF-0F51271B5E82@.microsoft.com...
> Hi,
> I have two servers within the same domain. Using CMD Prompt, when I copy
> files from one server to another, it works flawlessly, eg. COPY
> D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
> However, when I use the same command in a CMDEXEC step of a job, it gives
me
> an Access Denied error message.
> Any help. Thanks in advance for all your help.
copy files
Hi,
I have two servers within the same domain. Using CMD Prompt, when I copy
files from one server to another, it works flawlessly, eg. COPY
D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
However, when I use the same command in a CMDEXEC step of a job, it gives me
an Access Denied error message.
Any help. Thanks in advance for all your help.Make sure that the account that the SQL Server Agent runs in has permissions
on the source/ destination. Thats the account that jobs run in.
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:3FED8D10-A43F-431A-94EF-0F51271B5E82@.microsoft.com...
> Hi,
> I have two servers within the same domain. Using CMD Prompt, when I copy
> files from one server to another, it works flawlessly, eg. COPY
> D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
> However, when I use the same command in a CMDEXEC step of a job, it gives
me
> an Access Denied error message.
> Any help. Thanks in advance for all your help.
I have two servers within the same domain. Using CMD Prompt, when I copy
files from one server to another, it works flawlessly, eg. COPY
D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
However, when I use the same command in a CMDEXEC step of a job, it gives me
an Access Denied error message.
Any help. Thanks in advance for all your help.Make sure that the account that the SQL Server Agent runs in has permissions
on the source/ destination. Thats the account that jobs run in.
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:3FED8D10-A43F-431A-94EF-0F51271B5E82@.microsoft.com...
> Hi,
> I have two servers within the same domain. Using CMD Prompt, when I copy
> files from one server to another, it works flawlessly, eg. COPY
> D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
> However, when I use the same command in a CMDEXEC step of a job, it gives
me
> an Access Denied error message.
> Any help. Thanks in advance for all your help.
copy files
Hi,
I have two servers within the same domain. Using CMD Prompt, when I copy
files from one server to another, it works flawlessly, eg. COPY
D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
However, when I use the same command in a CMDEXEC step of a job, it gives me
an Access Denied error message.
Any help. Thanks in advance for all your help.
Make sure that the account that the SQL Server Agent runs in has permissions
on the source/ destination. Thats the account that jobs run in.
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:3FED8D10-A43F-431A-94EF-0F51271B5E82@.microsoft.com...
> Hi,
> I have two servers within the same domain. Using CMD Prompt, when I copy
> files from one server to another, it works flawlessly, eg. COPY
> D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
> However, when I use the same command in a CMDEXEC step of a job, it gives
me
> an Access Denied error message.
> Any help. Thanks in advance for all your help.
I have two servers within the same domain. Using CMD Prompt, when I copy
files from one server to another, it works flawlessly, eg. COPY
D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
However, when I use the same command in a CMDEXEC step of a job, it gives me
an Access Denied error message.
Any help. Thanks in advance for all your help.
Make sure that the account that the SQL Server Agent runs in has permissions
on the source/ destination. Thats the account that jobs run in.
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:3FED8D10-A43F-431A-94EF-0F51271B5E82@.microsoft.com...
> Hi,
> I have two servers within the same domain. Using CMD Prompt, when I copy
> files from one server to another, it works flawlessly, eg. COPY
> D:\SQL8Bkup4DRP\*.BAK \\<otherServerName>\D$\SQL8Bkup4DRP
> However, when I use the same command in a CMDEXEC step of a job, it gives
me
> an Access Denied error message.
> Any help. Thanks in advance for all your help.
Sunday, March 25, 2012
Copy DB fails (at Create Package step) SQL 2005
Copying a db is an easy task under 2000, but 05...
New install of SQL05 on Windows03R2, the machine is a AD domain controller
(one and only in a test forest), SQL services run under an account with
Domain Admin and built-in\Administrators rights. All components (engine,
Integration services, etc) are installed to an E: volume and all services
run under the SQL-Services account I created. No errors anywhere, creating
a test db is fine.
Using the "Copy Database Wizard" fails at the "Create Package" step no
matter if "detach and attach" or "SQL mgnt object" method is used with the
same error (see below). Just a simple one table test db can not be copied
to the same server using the "copy db wizard" in SQL Server 2005.
It looks like the copy package can not be written to the MSDB. The create
package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
tried all kind of things - Giving the SQL-Services account db_owner rights
to MSDB (it should already have this from its sysadmin role and membership
in AD/Domain Admins built-in\admins). If there is something wrong with
using the "SQL Server Agent Service Account" as the Integration Services
Proxy account, I created security credentials and a Agent Proxy - but no
go - the wizard always fails at the create package step.
Please help, what am I missing?
===================================
No description found (Copy Database Wizard)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveTo SqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.SqlServer.Management.CopyDatabaseWizard. PackageCreator.SavePackage()
A little more investigation revealed that SS Business Intelligence DS will
not save a package to the server (it gets a similar error – see below) and
the maintenance plan designer will not save a plan (it gets a "no description
found" error).
So there must be something seriously wrong with the SQL Server 2005
installation routine.
Maybe the installation failed (without error) because I at first installed
only some components to the E: drive and the rest of the components to the C:
drive. The installation screens are VERY poor in clearly describing what
will be installed where. So after I realized a bunch of components got
installed to C: and that the copy of Visual Studio that comes with SQL server
05 was installed to C: and that this would then FORCE the full version of VS
to C: I completely uninstalled SQL 2005.
I reinstalled all components to E: and then installed the full version of VS
(also to E
– all without error.
It is likely that the SQL Server 2005 installation routine is fragile – and
it does not tell you about all errors it encounters. This is in complete
contrast to the SQL Server 2000 bullet proof installation routine.
I will do another complete uninstall of SQL 2005 and reinstall to see if
this helps.
Note, others have also reported this problem but not first with the copy db
wizard. Here is one:
http://forums.microsoft.com/MSDN/Sho...29472&SiteID=1
MikeC
Error from create SSIS package:
===================================
No description found (Microsoft Visual Studio)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveTo SqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.DataTransformationServices.Controls.Pack ageLocationControl.SavePackage(Package package)
at
Microsoft.DataTransformationServices.Design.Contro ls.PackageSaveCopyForm.PackageSaveCopyForm_FormClo sing(Object sender, FormClosingEventArgs e)
"MikeC" wrote:
> Copying a db is an easy task under 2000, but 05...
> New install of SQL05 on Windows03R2, the machine is a AD domain controller
> (one and only in a test forest), SQL services run under an account with
> Domain Admin and built-in\Administrators rights. All components (engine,
> Integration services, etc) are installed to an E: volume and all services
> run under the SQL-Services account I created. No errors anywhere, creating
> a test db is fine.
> Using the "Copy Database Wizard" fails at the "Create Package" step no
> matter if "detach and attach" or "SQL mgnt object" method is used with the
> same error (see below). Just a simple one table test db can not be copied
> to the same server using the "copy db wizard" in SQL Server 2005.
> It looks like the copy package can not be written to the MSDB. The create
> package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
> tried all kind of things - Giving the SQL-Services account db_owner rights
> to MSDB (it should already have this from its sysadmin role and membership
> in AD/Domain Admins built-in\admins). If there is something wrong with
> using the "SQL Server Agent Service Account" as the Integration Services
> Proxy account, I created security credentials and a Agent Proxy - but no
> go - the wizard always fails at the create package step.
> Please help, what am I missing?
>
> ===================================
> No description found (Copy Database Wizard)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.Application.SaveTo SqlServerAs(Package
> package, IDTSEvents events, String packagePath, String serverName, String
> serverUserName, String serverPassword)
> at
> Microsoft.SqlServer.Management.CopyDatabaseWizard. PackageCreator.SavePackage()
>
>
|||I completely uninstalled SQL Server 2005 and all components - AGAIN.
This time, I deleted all remnants of SQL from the registry and file system -
SQL 2005 uninstall apparently is not as good as the SQL 2000 uninstall...
I reinstalled all components - and now saving packages works, including the
db copy wizard. Why? SQL 2005 install must have an intermittent bug or
something…
Now, have noticed a small bug with service status display, but it is minor.
When will we see SQL 2005 service pack one?
MikeC
|||The failure to create a package on Win03R2/SQL05 is back!
This time, SSIS package saving worked fine for a while. I copied a few
development dbs over to 2005, then went away and did some other work on
SharePoint Services setup.
The server was rebooted and I ran the SQL setup - only to the point of
looking at what was installed - oddly the complete list of installed
components in setup is un-checked. I was looking for the SQL Server Mobile
components - they are not installed and I did not install them.
Anyway the problem is back. So it it not really an install problem. More
trouble-shooting is in order - the absolutely minimal error information
provided does not make it easy.
Have you seen this problem? Help!
MikeC
|||It looks like reinstalling VS05pro after installing SQL05dev on Win03R2
CORRUPTS SQL Server 2005 Integration Services (a package cannot be saved to
server).
If I do the SQL05 install last, I avoid the problem. Now the question is -
what exactly gets corrupted and will this problem reappear when the VS SP1
comes out?
I think SQL Server 2000 was one of the best products that Microsoft created.
The SQL 2000 install was so simple and well behaved. Now, M$ has made SQL
Server into a monsters mess of DCOM linkages and registry bloat. Is it too
much to ask that M$ provide a simple install routine, one that displays a
manifest of files installed, and a list of registry changes? Maybe they are
ashamed of the mass of horrific registry db linkages put in to prop-up their
database “programming” model and want to pretend its not there…
MikeC
|||SQL05 creators - you must be joking - when you choose the Copy Database
""Wizard"" by right clicking on an existing db and then connect to another
server as a *source* you automatically select the local database as a copy
source **IN-ADDITION** to the db that a user needs to select on the remote
server.
In this case the remote db gets copied AND the local db gets copied - two
copies at the same time, so wacky! Just put in a copy db button to fix your
dangerous db copy interface.
MikeC
sqlsql
New install of SQL05 on Windows03R2, the machine is a AD domain controller
(one and only in a test forest), SQL services run under an account with
Domain Admin and built-in\Administrators rights. All components (engine,
Integration services, etc) are installed to an E: volume and all services
run under the SQL-Services account I created. No errors anywhere, creating
a test db is fine.
Using the "Copy Database Wizard" fails at the "Create Package" step no
matter if "detach and attach" or "SQL mgnt object" method is used with the
same error (see below). Just a simple one table test db can not be copied
to the same server using the "copy db wizard" in SQL Server 2005.
It looks like the copy package can not be written to the MSDB. The create
package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
tried all kind of things - Giving the SQL-Services account db_owner rights
to MSDB (it should already have this from its sysadmin role and membership
in AD/Domain Admins built-in\admins). If there is something wrong with
using the "SQL Server Agent Service Account" as the Integration Services
Proxy account, I created security credentials and a Agent Proxy - but no
go - the wizard always fails at the create package step.
Please help, what am I missing?
===================================
No description found (Copy Database Wizard)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveTo SqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.SqlServer.Management.CopyDatabaseWizard. PackageCreator.SavePackage()
A little more investigation revealed that SS Business Intelligence DS will
not save a package to the server (it gets a similar error – see below) and
the maintenance plan designer will not save a plan (it gets a "no description
found" error).
So there must be something seriously wrong with the SQL Server 2005
installation routine.
Maybe the installation failed (without error) because I at first installed
only some components to the E: drive and the rest of the components to the C:
drive. The installation screens are VERY poor in clearly describing what
will be installed where. So after I realized a bunch of components got
installed to C: and that the copy of Visual Studio that comes with SQL server
05 was installed to C: and that this would then FORCE the full version of VS
to C: I completely uninstalled SQL 2005.
I reinstalled all components to E: and then installed the full version of VS
(also to E
– all without error.It is likely that the SQL Server 2005 installation routine is fragile – and
it does not tell you about all errors it encounters. This is in complete
contrast to the SQL Server 2000 bullet proof installation routine.
I will do another complete uninstall of SQL 2005 and reinstall to see if
this helps.
Note, others have also reported this problem but not first with the copy db
wizard. Here is one:
http://forums.microsoft.com/MSDN/Sho...29472&SiteID=1
MikeC
Error from create SSIS package:
===================================
No description found (Microsoft Visual Studio)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveTo SqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.DataTransformationServices.Controls.Pack ageLocationControl.SavePackage(Package package)
at
Microsoft.DataTransformationServices.Design.Contro ls.PackageSaveCopyForm.PackageSaveCopyForm_FormClo sing(Object sender, FormClosingEventArgs e)
"MikeC" wrote:
> Copying a db is an easy task under 2000, but 05...
> New install of SQL05 on Windows03R2, the machine is a AD domain controller
> (one and only in a test forest), SQL services run under an account with
> Domain Admin and built-in\Administrators rights. All components (engine,
> Integration services, etc) are installed to an E: volume and all services
> run under the SQL-Services account I created. No errors anywhere, creating
> a test db is fine.
> Using the "Copy Database Wizard" fails at the "Create Package" step no
> matter if "detach and attach" or "SQL mgnt object" method is used with the
> same error (see below). Just a simple one table test db can not be copied
> to the same server using the "copy db wizard" in SQL Server 2005.
> It looks like the copy package can not be written to the MSDB. The create
> package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
> tried all kind of things - Giving the SQL-Services account db_owner rights
> to MSDB (it should already have this from its sysadmin role and membership
> in AD/Domain Admins built-in\admins). If there is something wrong with
> using the "SQL Server Agent Service Account" as the Integration Services
> Proxy account, I created security credentials and a Agent Proxy - but no
> go - the wizard always fails at the create package step.
> Please help, what am I missing?
>
> ===================================
> No description found (Copy Database Wizard)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.Application.SaveTo SqlServerAs(Package
> package, IDTSEvents events, String packagePath, String serverName, String
> serverUserName, String serverPassword)
> at
> Microsoft.SqlServer.Management.CopyDatabaseWizard. PackageCreator.SavePackage()
>
>
|||I completely uninstalled SQL Server 2005 and all components - AGAIN.
This time, I deleted all remnants of SQL from the registry and file system -
SQL 2005 uninstall apparently is not as good as the SQL 2000 uninstall...
I reinstalled all components - and now saving packages works, including the
db copy wizard. Why? SQL 2005 install must have an intermittent bug or
something…
Now, have noticed a small bug with service status display, but it is minor.
When will we see SQL 2005 service pack one?
MikeC
|||The failure to create a package on Win03R2/SQL05 is back!
This time, SSIS package saving worked fine for a while. I copied a few
development dbs over to 2005, then went away and did some other work on
SharePoint Services setup.
The server was rebooted and I ran the SQL setup - only to the point of
looking at what was installed - oddly the complete list of installed
components in setup is un-checked. I was looking for the SQL Server Mobile
components - they are not installed and I did not install them.
Anyway the problem is back. So it it not really an install problem. More
trouble-shooting is in order - the absolutely minimal error information
provided does not make it easy.
Have you seen this problem? Help!
MikeC
|||It looks like reinstalling VS05pro after installing SQL05dev on Win03R2
CORRUPTS SQL Server 2005 Integration Services (a package cannot be saved to
server).
If I do the SQL05 install last, I avoid the problem. Now the question is -
what exactly gets corrupted and will this problem reappear when the VS SP1
comes out?
I think SQL Server 2000 was one of the best products that Microsoft created.
The SQL 2000 install was so simple and well behaved. Now, M$ has made SQL
Server into a monsters mess of DCOM linkages and registry bloat. Is it too
much to ask that M$ provide a simple install routine, one that displays a
manifest of files installed, and a list of registry changes? Maybe they are
ashamed of the mass of horrific registry db linkages put in to prop-up their
database “programming” model and want to pretend its not there…
MikeC
|||SQL05 creators - you must be joking - when you choose the Copy Database
""Wizard"" by right clicking on an existing db and then connect to another
server as a *source* you automatically select the local database as a copy
source **IN-ADDITION** to the db that a user needs to select on the remote
server.
In this case the remote db gets copied AND the local db gets copied - two
copies at the same time, so wacky! Just put in a copy db button to fix your
dangerous db copy interface.
MikeC
sqlsql
Copy DB fails (at Create Package step) SQL 2005
Copying a db is an easy task under 2000, but 05...
New install of SQL05 on Windows03R2, the machine is a AD domain controller
(one and only in a test forest), SQL services run under an account with
Domain Admin and built-in\Administrators rights. All components (engine,
Integration services, etc) are installed to an E: volume and all services
run under the SQL-Services account I created. No errors anywhere, creating
a test db is fine.
Using the "Copy Database Wizard" fails at the "Create Package" step no
matter if "detach and attach" or "SQL mgnt object" method is used with the
same error (see below). Just a simple one table test db can not be copied
to the same server using the "copy db wizard" in SQL Server 2005.
It looks like the copy package can not be written to the MSDB. The create
package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
tried all kind of things - Giving the SQL-Services account db_owner rights
to MSDB (it should already have this from its sysadmin role and membership
in AD/Domain Admins built-in\admins). If there is something wrong with
using the "SQL Server Agent Service Account" as the Integration Services
Proxy account, I created security credentials and a Agent Proxy - but no
go - the wizard always fails at the create package step.
Please help, what am I missing?
===================================
No description found (Copy Database Wizard)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage
()A little more investigation revealed that SS Business Intelligence DS will
not save a package to the server (it gets a similar error – see below) and
the maintenance plan designer will not save a plan (it gets a "no descriptio
n
found" error).
So there must be something seriously wrong with the SQL Server 2005
installation routine.
Maybe the installation failed (without error) because I at first installed
only some components to the E: drive and the rest of the components to the C
:
drive. The installation screens are VERY poor in clearly describing what
will be installed where. So after I realized a bunch of components got
installed to C: and that the copy of Visual Studio that comes with SQL serve
r
05 was installed to C: and that this would then FORCE the full version of VS
to C: I completely uninstalled SQL 2005.
I reinstalled all components to E: and then installed the full version of VS
(also to E – all without error.
It is likely that the SQL Server 2005 installation routine is fragile – an
d
it does not tell you about all errors it encounters. This is in complete
contrast to the SQL Server 2000 bullet proof installation routine.
I will do another complete uninstall of SQL 2005 and reinstall to see if
this helps.
Note, others have also reported this problem but not first with the copy db
wizard. Here is one:
http://forums.microsoft.com/MSDN/Sh...129472&SiteID=1
MikeC
Error from create SSIS package:
===================================
No description found (Microsoft Visual Studio)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePac
kage(Package package)
at
Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.Pac
kageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)
"MikeC" wrote:
> Copying a db is an easy task under 2000, but 05...
> New install of SQL05 on Windows03R2, the machine is a AD domain controller
> (one and only in a test forest), SQL services run under an account with
> Domain Admin and built-in\Administrators rights. All components (engine,
> Integration services, etc) are installed to an E: volume and all services
> run under the SQL-Services account I created. No errors anywhere, creatin
g
> a test db is fine.
> Using the "Copy Database Wizard" fails at the "Create Package" step no
> matter if "detach and attach" or "SQL mgnt object" method is used with the
> same error (see below). Just a simple one table test db can not be copied
> to the same server using the "copy db wizard" in SQL Server 2005.
> It looks like the copy package can not be written to the MSDB. The create
> package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I hav
e
> tried all kind of things - Giving the SQL-Services account db_owner rights
> to MSDB (it should already have this from its sysadmin role and membership
> in AD/Domain Admins built-in\admins). If there is something wrong with
> using the "SQL Server Agent Service Account" as the Integration Services
> Proxy account, I created security credentials and a Agent Proxy - but no
> go - the wizard always fails at the create package step.
> Please help, what am I missing?
>
> ===================================
> No description found (Copy Database Wizard)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Packag
e
> package, IDTSEvents events, String packagePath, String serverName, String
> serverUserName, String serverPassword)
> at
> Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePacka
ge()
>
>|||I completely uninstalled SQL Server 2005 and all components - AGAIN.
This time, I deleted all remnants of SQL from the registry and file system -
SQL 2005 uninstall apparently is not as good as the SQL 2000 uninstall...
I reinstalled all components - and now saving packages works, including the
db copy wizard. Why? SQL 2005 install must have an intermittent bug or
something…
Now, have noticed a small bug with service status display, but it is minor.
When will we see SQL 2005 service pack one?
MikeC|||The failure to create a package on Win03R2/SQL05 is back!
This time, SSIS package saving worked fine for a while. I copied a few
development dbs over to 2005, then went away and did some other work on
SharePoint Services setup.
The server was rebooted and I ran the SQL setup - only to the point of
looking at what was installed - oddly the complete list of installed
components in setup is un-checked. I was looking for the SQL Server Mobile
components - they are not installed and I did not install them.
Anyway the problem is back. So it it not really an install problem. More
trouble-shooting is in order - the absolutely minimal error information
provided does not make it easy.
Have you seen this problem? Help!
MikeC|||It looks like reinstalling VS05pro after installing SQL05dev on Win03R2
CORRUPTS SQL Server 2005 Integration Services (a package cannot be saved to
server).
If I do the SQL05 install last, I avoid the problem. Now the question is -
what exactly gets corrupted and will this problem reappear when the VS SP1
comes out?
I think SQL Server 2000 was one of the best products that Microsoft created.
The SQL 2000 install was so simple and well behaved. Now, M$ has made SQL
Server into a monsters mess of DCOM linkages and registry bloat. Is it too
much to ask that M$ provide a simple install routine, one that displays a
manifest of files installed, and a list of registry changes? Maybe they are
ashamed of the mass of horrific registry db linkages put in to prop-up their
database “programming” model and want to pretend its not there…
MikeC|||SQL05 creators - you must be joking - when you choose the Copy Database
""Wizard"" by right clicking on an existing db and then connect to another
server as a *source* you automatically select the local database as a copy
source **IN-ADDITION** to the db that a user needs to select on the remote
server.
In this case the remote db gets copied AND the local db gets copied - two
copies at the same time, so wacky! Just put in a copy db button to fix your
dangerous db copy interface.
MikeC
New install of SQL05 on Windows03R2, the machine is a AD domain controller
(one and only in a test forest), SQL services run under an account with
Domain Admin and built-in\Administrators rights. All components (engine,
Integration services, etc) are installed to an E: volume and all services
run under the SQL-Services account I created. No errors anywhere, creating
a test db is fine.
Using the "Copy Database Wizard" fails at the "Create Package" step no
matter if "detach and attach" or "SQL mgnt object" method is used with the
same error (see below). Just a simple one table test db can not be copied
to the same server using the "copy db wizard" in SQL Server 2005.
It looks like the copy package can not be written to the MSDB. The create
package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
tried all kind of things - Giving the SQL-Services account db_owner rights
to MSDB (it should already have this from its sysadmin role and membership
in AD/Domain Admins built-in\admins). If there is something wrong with
using the "SQL Server Agent Service Account" as the Integration Services
Proxy account, I created security credentials and a Agent Proxy - but no
go - the wizard always fails at the create package step.
Please help, what am I missing?
===================================
No description found (Copy Database Wizard)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage
()A little more investigation revealed that SS Business Intelligence DS will
not save a package to the server (it gets a similar error – see below) and
the maintenance plan designer will not save a plan (it gets a "no descriptio
n
found" error).
So there must be something seriously wrong with the SQL Server 2005
installation routine.
Maybe the installation failed (without error) because I at first installed
only some components to the E: drive and the rest of the components to the C
:
drive. The installation screens are VERY poor in clearly describing what
will be installed where. So after I realized a bunch of components got
installed to C: and that the copy of Visual Studio that comes with SQL serve
r
05 was installed to C: and that this would then FORCE the full version of VS
to C: I completely uninstalled SQL 2005.
I reinstalled all components to E: and then installed the full version of VS
(also to E
– all without error.It is likely that the SQL Server 2005 installation routine is fragile – an
d
it does not tell you about all errors it encounters. This is in complete
contrast to the SQL Server 2000 bullet proof installation routine.
I will do another complete uninstall of SQL 2005 and reinstall to see if
this helps.
Note, others have also reported this problem but not first with the copy db
wizard. Here is one:
http://forums.microsoft.com/MSDN/Sh...129472&SiteID=1
MikeC
Error from create SSIS package:
===================================
No description found (Microsoft Visual Studio)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePac
kage(Package package)
at
Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.Pac
kageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)
"MikeC" wrote:
> Copying a db is an easy task under 2000, but 05...
> New install of SQL05 on Windows03R2, the machine is a AD domain controller
> (one and only in a test forest), SQL services run under an account with
> Domain Admin and built-in\Administrators rights. All components (engine,
> Integration services, etc) are installed to an E: volume and all services
> run under the SQL-Services account I created. No errors anywhere, creatin
g
> a test db is fine.
> Using the "Copy Database Wizard" fails at the "Create Package" step no
> matter if "detach and attach" or "SQL mgnt object" method is used with the
> same error (see below). Just a simple one table test db can not be copied
> to the same server using the "copy db wizard" in SQL Server 2005.
> It looks like the copy package can not be written to the MSDB. The create
> package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I hav
e
> tried all kind of things - Giving the SQL-Services account db_owner rights
> to MSDB (it should already have this from its sysadmin role and membership
> in AD/Domain Admins built-in\admins). If there is something wrong with
> using the "SQL Server Agent Service Account" as the Integration Services
> Proxy account, I created security credentials and a Agent Proxy - but no
> go - the wizard always fails at the create package step.
> Please help, what am I missing?
>
> ===================================
> No description found (Copy Database Wizard)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Packag
e
> package, IDTSEvents events, String packagePath, String serverName, String
> serverUserName, String serverPassword)
> at
> Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePacka
ge()
>
>|||I completely uninstalled SQL Server 2005 and all components - AGAIN.
This time, I deleted all remnants of SQL from the registry and file system -
SQL 2005 uninstall apparently is not as good as the SQL 2000 uninstall...
I reinstalled all components - and now saving packages works, including the
db copy wizard. Why? SQL 2005 install must have an intermittent bug or
something…
Now, have noticed a small bug with service status display, but it is minor.
When will we see SQL 2005 service pack one?
MikeC|||The failure to create a package on Win03R2/SQL05 is back!
This time, SSIS package saving worked fine for a while. I copied a few
development dbs over to 2005, then went away and did some other work on
SharePoint Services setup.
The server was rebooted and I ran the SQL setup - only to the point of
looking at what was installed - oddly the complete list of installed
components in setup is un-checked. I was looking for the SQL Server Mobile
components - they are not installed and I did not install them.
Anyway the problem is back. So it it not really an install problem. More
trouble-shooting is in order - the absolutely minimal error information
provided does not make it easy.
Have you seen this problem? Help!
MikeC|||It looks like reinstalling VS05pro after installing SQL05dev on Win03R2
CORRUPTS SQL Server 2005 Integration Services (a package cannot be saved to
server).
If I do the SQL05 install last, I avoid the problem. Now the question is -
what exactly gets corrupted and will this problem reappear when the VS SP1
comes out?
I think SQL Server 2000 was one of the best products that Microsoft created.
The SQL 2000 install was so simple and well behaved. Now, M$ has made SQL
Server into a monsters mess of DCOM linkages and registry bloat. Is it too
much to ask that M$ provide a simple install routine, one that displays a
manifest of files installed, and a list of registry changes? Maybe they are
ashamed of the mass of horrific registry db linkages put in to prop-up their
database “programming” model and want to pretend its not there…
MikeC|||SQL05 creators - you must be joking - when you choose the Copy Database
""Wizard"" by right clicking on an existing db and then connect to another
server as a *source* you automatically select the local database as a copy
source **IN-ADDITION** to the db that a user needs to select on the remote
server.
In this case the remote db gets copied AND the local db gets copied - two
copies at the same time, so wacky! Just put in a copy db button to fix your
dangerous db copy interface.
MikeC
Copy DB fails (at Create Package step) SQL 2005
Copying a db is an easy task under 2000, but 05...
New install of SQL05 on Windows03R2, the machine is a AD domain controller
(one and only in a test forest), SQL services run under an account with
Domain Admin and built-in\Administrators rights. All components (engine,
Integration services, etc) are installed to an E: volume and all services
run under the SQL-Services account I created. No errors anywhere, creating
a test db is fine.
Using the "Copy Database Wizard" fails at the "Create Package" step no
matter if "detach and attach" or "SQL mgnt object" method is used with the
same error (see below). Just a simple one table test db can not be copied
to the same server using the "copy db wizard" in SQL Server 2005.
It looks like the copy package can not be written to the MSDB. The create
package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
tried all kind of things - Giving the SQL-Services account db_owner rights
to MSDB (it should already have this from its sysadmin role and membership
in AD/Domain Admins built-in\admins). If there is something wrong with
using the "SQL Server Agent Service Account" as the Integration Services
Proxy account, I created security credentials and a Agent Proxy - but no
go - the wizard always fails at the create package step.
Please help, what am I missing?
=================================== No description found (Copy Database Wizard)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()A little more investigation revealed that SS Business Intelligence DS will
not save a package to the server (it gets a similar error â' see below) and
the maintenance plan designer will not save a plan (it gets a "no description
found" error).
So there must be something seriously wrong with the SQL Server 2005
installation routine.
Maybe the installation failed (without error) because I at first installed
only some components to the E: drive and the rest of the components to the C:
drive. The installation screens are VERY poor in clearly describing what
will be installed where. So after I realized a bunch of components got
installed to C: and that the copy of Visual Studio that comes with SQL server
05 was installed to C: and that this would then FORCE the full version of VS
to C: I completely uninstalled SQL 2005.
I reinstalled all components to E: and then installed the full version of VS
(also to E:) â' all without error.
It is likely that the SQL Server 2005 installation routine is fragile â' and
it does not tell you about all errors it encounters. This is in complete
contrast to the SQL Server 2000 bullet proof installation routine.
I will do another complete uninstall of SQL 2005 and reinstall to see if
this helps.
Note, others have also reported this problem but not first with the copy db
wizard. Here is one:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=129472&SiteID=1
MikeC
Error from create SSIS package:
===================================
No description found (Microsoft Visual Studio)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package)
at
Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)
"MikeC" wrote:
> Copying a db is an easy task under 2000, but 05...
> New install of SQL05 on Windows03R2, the machine is a AD domain controller
> (one and only in a test forest), SQL services run under an account with
> Domain Admin and built-in\Administrators rights. All components (engine,
> Integration services, etc) are installed to an E: volume and all services
> run under the SQL-Services account I created. No errors anywhere, creating
> a test db is fine.
> Using the "Copy Database Wizard" fails at the "Create Package" step no
> matter if "detach and attach" or "SQL mgnt object" method is used with the
> same error (see below). Just a simple one table test db can not be copied
> to the same server using the "copy db wizard" in SQL Server 2005.
> It looks like the copy package can not be written to the MSDB. The create
> package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
> tried all kind of things - Giving the SQL-Services account db_owner rights
> to MSDB (it should already have this from its sysadmin role and membership
> in AD/Domain Admins built-in\admins). If there is something wrong with
> using the "SQL Server Agent Service Account" as the Integration Services
> Proxy account, I created security credentials and a Agent Proxy - but no
> go - the wizard always fails at the create package step.
> Please help, what am I missing?
>
> ===================================> No description found (Copy Database Wizard)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
> package, IDTSEvents events, String packagePath, String serverName, String
> serverUserName, String serverPassword)
> at
> Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()
>
>|||I completely uninstalled SQL Server 2005 and all components - AGAIN.
This time, I deleted all remnants of SQL from the registry and file system -
SQL 2005 uninstall apparently is not as good as the SQL 2000 uninstall...
I reinstalled all components - and now saving packages works, including the
db copy wizard. Why? SQL 2005 install must have an intermittent bug or
somethingâ?¦
Now, have noticed a small bug with service status display, but it is minor.
When will we see SQL 2005 service pack one?
MikeC|||The failure to create a package on Win03R2/SQL05 is back!
This time, SSIS package saving worked fine for a while. I copied a few
development dbs over to 2005, then went away and did some other work on
SharePoint Services setup.
The server was rebooted and I ran the SQL setup - only to the point of
looking at what was installed - oddly the complete list of installed
components in setup is un-checked. I was looking for the SQL Server Mobile
components - they are not installed and I did not install them.
Anyway the problem is back. So it it not really an install problem. More
trouble-shooting is in order - the absolutely minimal error information
provided does not make it easy.
Have you seen this problem? Help!
MikeC|||It looks like reinstalling VS05pro after installing SQL05dev on Win03R2
CORRUPTS SQL Server 2005 Integration Services (a package cannot be saved to
server).
If I do the SQL05 install last, I avoid the problem. Now the question is -
what exactly gets corrupted and will this problem reappear when the VS SP1
comes out?
I think SQL Server 2000 was one of the best products that Microsoft created.
The SQL 2000 install was so simple and well behaved. Now, M$ has made SQL
Server into a monsters mess of DCOM linkages and registry bloat. Is it too
much to ask that M$ provide a simple install routine, one that displays a
manifest of files installed, and a list of registry changes? Maybe they are
ashamed of the mass of horrific registry db linkages put in to prop-up their
database â'programmingâ' model and want to pretend its not thereâ?¦
MikeC|||SQL05 creators - you must be joking - when you choose the Copy Database
""Wizard"" by right clicking on an existing db and then connect to another
server as a *source* you automatically select the local database as a copy
source **IN-ADDITION** to the db that a user needs to select on the remote
server.
In this case the remote db gets copied AND the local db gets copied - two
copies at the same time, so wacky! Just put in a copy db button to fix your
dangerous db copy interface.
MikeC
New install of SQL05 on Windows03R2, the machine is a AD domain controller
(one and only in a test forest), SQL services run under an account with
Domain Admin and built-in\Administrators rights. All components (engine,
Integration services, etc) are installed to an E: volume and all services
run under the SQL-Services account I created. No errors anywhere, creating
a test db is fine.
Using the "Copy Database Wizard" fails at the "Create Package" step no
matter if "detach and attach" or "SQL mgnt object" method is used with the
same error (see below). Just a simple one table test db can not be copied
to the same server using the "copy db wizard" in SQL Server 2005.
It looks like the copy package can not be written to the MSDB. The create
package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
tried all kind of things - Giving the SQL-Services account db_owner rights
to MSDB (it should already have this from its sysadmin role and membership
in AD/Domain Admins built-in\admins). If there is something wrong with
using the "SQL Server Agent Service Account" as the Integration Services
Proxy account, I created security credentials and a Agent Proxy - but no
go - the wizard always fails at the create package step.
Please help, what am I missing?
=================================== No description found (Copy Database Wizard)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()A little more investigation revealed that SS Business Intelligence DS will
not save a package to the server (it gets a similar error â' see below) and
the maintenance plan designer will not save a plan (it gets a "no description
found" error).
So there must be something seriously wrong with the SQL Server 2005
installation routine.
Maybe the installation failed (without error) because I at first installed
only some components to the E: drive and the rest of the components to the C:
drive. The installation screens are VERY poor in clearly describing what
will be installed where. So after I realized a bunch of components got
installed to C: and that the copy of Visual Studio that comes with SQL server
05 was installed to C: and that this would then FORCE the full version of VS
to C: I completely uninstalled SQL 2005.
I reinstalled all components to E: and then installed the full version of VS
(also to E:) â' all without error.
It is likely that the SQL Server 2005 installation routine is fragile â' and
it does not tell you about all errors it encounters. This is in complete
contrast to the SQL Server 2000 bullet proof installation routine.
I will do another complete uninstall of SQL 2005 and reinstall to see if
this helps.
Note, others have also reported this problem but not first with the copy db
wizard. Here is one:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=129472&SiteID=1
MikeC
Error from create SSIS package:
===================================
No description found (Microsoft Visual Studio)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
package, IDTSEvents events, String packagePath, String serverName, String
serverUserName, String serverPassword)
at
Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package)
at
Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)
"MikeC" wrote:
> Copying a db is an easy task under 2000, but 05...
> New install of SQL05 on Windows03R2, the machine is a AD domain controller
> (one and only in a test forest), SQL services run under an account with
> Domain Admin and built-in\Administrators rights. All components (engine,
> Integration services, etc) are installed to an E: volume and all services
> run under the SQL-Services account I created. No errors anywhere, creating
> a test db is fine.
> Using the "Copy Database Wizard" fails at the "Create Package" step no
> matter if "detach and attach" or "SQL mgnt object" method is used with the
> same error (see below). Just a simple one table test db can not be copied
> to the same server using the "copy db wizard" in SQL Server 2005.
> It looks like the copy package can not be written to the MSDB. The create
> package is step 3 of 5, step 1 (add log) and 2 (add task) work ok. I have
> tried all kind of things - Giving the SQL-Services account db_owner rights
> to MSDB (it should already have this from its sysadmin role and membership
> in AD/Domain Admins built-in\admins). If there is something wrong with
> using the "SQL Server Agent Service Account" as the Integration Services
> Proxy account, I created security credentials and a Agent Proxy - but no
> go - the wizard always fails at the create package step.
> Please help, what am I missing?
>
> ===================================> No description found (Copy Database Wizard)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServerAs(Package
> package, IDTSEvents events, String packagePath, String serverName, String
> serverUserName, String serverPassword)
> at
> Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()
>
>|||I completely uninstalled SQL Server 2005 and all components - AGAIN.
This time, I deleted all remnants of SQL from the registry and file system -
SQL 2005 uninstall apparently is not as good as the SQL 2000 uninstall...
I reinstalled all components - and now saving packages works, including the
db copy wizard. Why? SQL 2005 install must have an intermittent bug or
somethingâ?¦
Now, have noticed a small bug with service status display, but it is minor.
When will we see SQL 2005 service pack one?
MikeC|||The failure to create a package on Win03R2/SQL05 is back!
This time, SSIS package saving worked fine for a while. I copied a few
development dbs over to 2005, then went away and did some other work on
SharePoint Services setup.
The server was rebooted and I ran the SQL setup - only to the point of
looking at what was installed - oddly the complete list of installed
components in setup is un-checked. I was looking for the SQL Server Mobile
components - they are not installed and I did not install them.
Anyway the problem is back. So it it not really an install problem. More
trouble-shooting is in order - the absolutely minimal error information
provided does not make it easy.
Have you seen this problem? Help!
MikeC|||It looks like reinstalling VS05pro after installing SQL05dev on Win03R2
CORRUPTS SQL Server 2005 Integration Services (a package cannot be saved to
server).
If I do the SQL05 install last, I avoid the problem. Now the question is -
what exactly gets corrupted and will this problem reappear when the VS SP1
comes out?
I think SQL Server 2000 was one of the best products that Microsoft created.
The SQL 2000 install was so simple and well behaved. Now, M$ has made SQL
Server into a monsters mess of DCOM linkages and registry bloat. Is it too
much to ask that M$ provide a simple install routine, one that displays a
manifest of files installed, and a list of registry changes? Maybe they are
ashamed of the mass of horrific registry db linkages put in to prop-up their
database â'programmingâ' model and want to pretend its not thereâ?¦
MikeC|||SQL05 creators - you must be joking - when you choose the Copy Database
""Wizard"" by right clicking on an existing db and then connect to another
server as a *source* you automatically select the local database as a copy
source **IN-ADDITION** to the db that a user needs to select on the remote
server.
In this case the remote db gets copied AND the local db gets copied - two
copies at the same time, so wacky! Just put in a copy db button to fix your
dangerous db copy interface.
MikeC
copy databases
Hi, how can i copy databases from one server in one domain to another
server. Since the servers isnt in the same domain its not possible to do
with the copy in enterprise manager (even with same username and password on
Administrator). Is there som 3de party program to use for this? the customer
has nearly 100 databases and to manualy detach, copy and attach then is a
hell of a job.
/Per W.See if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Per W." <fungererikke@.ikkegyldig.no.invalid> wrote in message
news:e6udnk$95i$1@.troll.powertech.no...
Hi, how can i copy databases from one server in one domain to another
server. Since the servers isnt in the same domain its not possible to do
with the copy in enterprise manager (even with same username and password on
Administrator). Is there som 3de party program to use for this? the customer
has nearly 100 databases and to manualy detach, copy and attach then is a
hell of a job.
/Per W.|||"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> skrev i melding
news:uRVRAIVkGHA.5036@.TK2MSFTNGP04.phx.gbl...
> See if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
>
No, sorry. I have 2 SBS servers, one 2000 that i will move the database over
to the new 2003, and since both servers are up and running i cant do this,
and i need something to copy all databases since the databases are on
different folders on the harddisk then ther is a lot of job copying the
files manualy. I cant understand why MS have made restrictions on the copy
options in the enterprise manager since this is a situation where it will be
realy good to use.
/Per W.
server. Since the servers isnt in the same domain its not possible to do
with the copy in enterprise manager (even with same username and password on
Administrator). Is there som 3de party program to use for this? the customer
has nearly 100 databases and to manualy detach, copy and attach then is a
hell of a job.
/Per W.See if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Per W." <fungererikke@.ikkegyldig.no.invalid> wrote in message
news:e6udnk$95i$1@.troll.powertech.no...
Hi, how can i copy databases from one server in one domain to another
server. Since the servers isnt in the same domain its not possible to do
with the copy in enterprise manager (even with same username and password on
Administrator). Is there som 3de party program to use for this? the customer
has nearly 100 databases and to manualy detach, copy and attach then is a
hell of a job.
/Per W.|||"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> skrev i melding
news:uRVRAIVkGHA.5036@.TK2MSFTNGP04.phx.gbl...
> See if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
>
No, sorry. I have 2 SBS servers, one 2000 that i will move the database over
to the new 2003, and since both servers are up and running i cant do this,
and i need something to copy all databases since the databases are on
different folders on the harddisk then ther is a lot of job copying the
files manualy. I cant understand why MS have made restrictions on the copy
options in the enterprise manager since this is a situation where it will be
realy good to use.
/Per W.
Thursday, March 22, 2012
Copy Database Wizard and DTS Transfer Database Task don't work
Hello,
I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
2000. Both belong to the same domain and can see each other without
problems. A mutual registration of the other sql server in Enterprise
Manager is no problem.
One Server's operating system is win2003Server, the other one's is
Win2000Server.
In both servers the domain account I use for logging in and for
authentification purposes is a member of the server's local
administrators group. And the local administrators have sysadmin rights
in sql server 2000 via builtin\administrators.
After some tests I added my windows domain account explicitly as
sysadmin in both SQL-Servers.
The security mode is "mixed" (SQL-Login and Windows).
Trying to transfer a Test database with 1MB space fails. No matter
whether I use a Transfer Database Task or whether I use the Copy
Database Wizard (which also uses DTS in the background).
The Transfer Database Task needs FIVE minutes for the dialog window
"Transfer Database Properties" to reappear after clicking on the
tab-card [file locations].
Below the grid is a green check mark: Files are ready to be moved or
copied.".
Below that is a red X: Files on the source have the same name as on the
destination or there is not enough free disk space on the destination.
On both servers there is plenty of space (dozens of GB).
In the end I only get the error description "Unspecified error".
Doing the same with the Copy Database wizard" in the Grid beside the
..mdf file and the .ldf file shows the STATUS: OK
Below, again two error messages:
Name conflict: Type a new name into the Destination Files fields
Disk space: Change the destination or free disk space
At the same time is shown the space needed and available:
E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
So I run the job in the wizard immediately and get the following
errors:
Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
Step Error code: 80004005
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:700
Apparently DTS uses odbc and can not establish the connection despite
Sysadmin rights on both servers. I tried to specify the account sa of
sql server for authentication instead of using windows authentication
but that yields the same result.
Would someone know the solution?
Thank you.
Andreas.meyer@.dmc-group.de wrote:
> Hello,
> I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
> 2000. Both belong to the same domain and can see each other without
> problems. A mutual registration of the other sql server in Enterprise
> Manager is no problem.
> One Server's operating system is win2003Server, the other one's is
> Win2000Server.
> In both servers the domain account I use for logging in and for
> authentification purposes is a member of the server's local
> administrators group. And the local administrators have sysadmin rights
> in sql server 2000 via builtin\administrators.
> After some tests I added my windows domain account explicitly as
> sysadmin in both SQL-Servers.
> The security mode is "mixed" (SQL-Login and Windows).
> Trying to transfer a Test database with 1MB space fails. No matter
> whether I use a Transfer Database Task or whether I use the Copy
> Database Wizard (which also uses DTS in the background).
> The Transfer Database Task needs FIVE minutes for the dialog window
> "Transfer Database Properties" to reappear after clicking on the
> tab-card [file locations].
> Below the grid is a green check mark: Files are ready to be moved or
> copied.".
> Below that is a red X: Files on the source have the same name as on the
> destination or there is not enough free disk space on the destination.
> On both servers there is plenty of space (dozens of GB).
> In the end I only get the error description "Unspecified error".
> Doing the same with the Copy Database wizard" in the Grid beside the
> .mdf file and the .ldf file shows the STATUS: OK
> Below, again two error messages:
> Name conflict: Type a new name into the Destination Files fields
> Disk space: Change the destination or free disk space
> At the same time is shown the space needed and available:
> E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
> So I run the job in the wizard immediately and get the following
> errors:
> Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
> Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
> Server]Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
> Step Error code: 80004005
> Step Error Help File:SQLDMO80.hlp
> Step Error Help Context ID:700
> Apparently DTS uses odbc and can not establish the connection despite
> Sysadmin rights on both servers. I tried to specify the account sa of
> sql server for authentication instead of using windows authentication
> but that yields the same result.
> Would someone know the solution?
> Thank you.
>
Save yourself the headache and stop using these wizards for such a
simple task. Simply take a backup of the source database, then restore
that onto the destination server. The syntax for the BACKUP and RESTORE
commands is pretty simple, see Books Online for details.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi Tracy,
of course, I did already.
However, there is so much fuss being made of what sql server 2000 can
do.
Also it is so much stressed in the exams: and dare you you wouldn't
know what the copy database wizard or DTS is able to to and that to use
it is so much easier and surely the best solution when asked for "the
least administrative effort", etc.
Then you try with one of the simplest tasks and in practice it just
fails in an environment where it is truly hard that it wouldn't work.
Yet it doesn't.
Nothing left any more of all the glory...
This is annoying.
Then again, I would like to know the reason for the error message in
odbc.
My impression is: a lot is just marketing but not working, really.
Sincerely
Andreas
Tracy McKibben schrieb:
> Andreas.meyer@.dmc-group.de wrote:
> Save yourself the headache and stop using these wizards for such a
> simple task. Simply take a backup of the source database, then restore
> that onto the destination server. The syntax for the BACKUP and RESTORE
> commands is pretty simple, see Books Online for details.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
2000. Both belong to the same domain and can see each other without
problems. A mutual registration of the other sql server in Enterprise
Manager is no problem.
One Server's operating system is win2003Server, the other one's is
Win2000Server.
In both servers the domain account I use for logging in and for
authentification purposes is a member of the server's local
administrators group. And the local administrators have sysadmin rights
in sql server 2000 via builtin\administrators.
After some tests I added my windows domain account explicitly as
sysadmin in both SQL-Servers.
The security mode is "mixed" (SQL-Login and Windows).
Trying to transfer a Test database with 1MB space fails. No matter
whether I use a Transfer Database Task or whether I use the Copy
Database Wizard (which also uses DTS in the background).
The Transfer Database Task needs FIVE minutes for the dialog window
"Transfer Database Properties" to reappear after clicking on the
tab-card [file locations].
Below the grid is a green check mark: Files are ready to be moved or
copied.".
Below that is a red X: Files on the source have the same name as on the
destination or there is not enough free disk space on the destination.
On both servers there is plenty of space (dozens of GB).
In the end I only get the error description "Unspecified error".
Doing the same with the Copy Database wizard" in the Grid beside the
..mdf file and the .ldf file shows the STATUS: OK
Below, again two error messages:
Name conflict: Type a new name into the Destination Files fields
Disk space: Change the destination or free disk space
At the same time is shown the space needed and available:
E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
So I run the job in the wizard immediately and get the following
errors:
Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
Step Error code: 80004005
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:700
Apparently DTS uses odbc and can not establish the connection despite
Sysadmin rights on both servers. I tried to specify the account sa of
sql server for authentication instead of using windows authentication
but that yields the same result.
Would someone know the solution?
Thank you.
Andreas.meyer@.dmc-group.de wrote:
> Hello,
> I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
> 2000. Both belong to the same domain and can see each other without
> problems. A mutual registration of the other sql server in Enterprise
> Manager is no problem.
> One Server's operating system is win2003Server, the other one's is
> Win2000Server.
> In both servers the domain account I use for logging in and for
> authentification purposes is a member of the server's local
> administrators group. And the local administrators have sysadmin rights
> in sql server 2000 via builtin\administrators.
> After some tests I added my windows domain account explicitly as
> sysadmin in both SQL-Servers.
> The security mode is "mixed" (SQL-Login and Windows).
> Trying to transfer a Test database with 1MB space fails. No matter
> whether I use a Transfer Database Task or whether I use the Copy
> Database Wizard (which also uses DTS in the background).
> The Transfer Database Task needs FIVE minutes for the dialog window
> "Transfer Database Properties" to reappear after clicking on the
> tab-card [file locations].
> Below the grid is a green check mark: Files are ready to be moved or
> copied.".
> Below that is a red X: Files on the source have the same name as on the
> destination or there is not enough free disk space on the destination.
> On both servers there is plenty of space (dozens of GB).
> In the end I only get the error description "Unspecified error".
> Doing the same with the Copy Database wizard" in the Grid beside the
> .mdf file and the .ldf file shows the STATUS: OK
> Below, again two error messages:
> Name conflict: Type a new name into the Destination Files fields
> Disk space: Change the destination or free disk space
> At the same time is shown the space needed and available:
> E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
> So I run the job in the wizard immediately and get the following
> errors:
> Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
> Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
> Server]Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
> Step Error code: 80004005
> Step Error Help File:SQLDMO80.hlp
> Step Error Help Context ID:700
> Apparently DTS uses odbc and can not establish the connection despite
> Sysadmin rights on both servers. I tried to specify the account sa of
> sql server for authentication instead of using windows authentication
> but that yields the same result.
> Would someone know the solution?
> Thank you.
>
Save yourself the headache and stop using these wizards for such a
simple task. Simply take a backup of the source database, then restore
that onto the destination server. The syntax for the BACKUP and RESTORE
commands is pretty simple, see Books Online for details.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi Tracy,
of course, I did already.
However, there is so much fuss being made of what sql server 2000 can
do.
Also it is so much stressed in the exams: and dare you you wouldn't
know what the copy database wizard or DTS is able to to and that to use
it is so much easier and surely the best solution when asked for "the
least administrative effort", etc.
Then you try with one of the simplest tasks and in practice it just
fails in an environment where it is truly hard that it wouldn't work.
Yet it doesn't.
Nothing left any more of all the glory...
This is annoying.
Then again, I would like to know the reason for the error message in
odbc.
My impression is: a lot is just marketing but not working, really.
Sincerely
Andreas
Tracy McKibben schrieb:
> Andreas.meyer@.dmc-group.de wrote:
> Save yourself the headache and stop using these wizards for such a
> simple task. Simply take a backup of the source database, then restore
> that onto the destination server. The syntax for the BACKUP and RESTORE
> commands is pretty simple, see Books Online for details.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Copy Database Wizard and DTS Transfer Database Task don't work
Hello,
I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
2000. Both belong to the same domain and can see each other without
problems. A mutual registration of the other sql server in Enterprise
Manager is no problem.
One Server's operating system is win2003Server, the other one's is
Win2000Server.
In both servers the domain account I use for logging in and for
authentification purposes is a member of the server's local
administrators group. And the local administrators have sysadmin rights
in sql server 2000 via builtin\administrators.
After some tests I added my windows domain account explicitly as
sysadmin in both SQL-Servers.
The security mode is "mixed" (SQL-Login and Windows).
Trying to transfer a Test database with 1MB space fails. No matter
whether I use a Transfer Database Task or whether I use the Copy
Database Wizard (which also uses DTS in the background).
The Transfer Database Task needs FIVE minutes for the dialog window
"Transfer Database Properties" to reappear after clicking on the
tab-card [file locations].
Below the grid is a green check mark: Files are ready to be moved or
copied.".
Below that is a red X: Files on the source have the same name as on the
destination or there is not enough free disk space on the destination.
On both servers there is plenty of space (dozens of GB).
In the end I only get the error description "Unspecified error".
Doing the same with the Copy Database wizard" in the Grid beside the
.mdf file and the .ldf file shows the STATUS: OK
Below, again two error messages:
Name conflict: Type a new name into the Destination Files fields
Disk space: Change the destination or free disk space
At the same time is shown the space needed and available:
E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
So I run the job in the wizard immediately and get the following
errors:
Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
Step Error code: 80004005
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:700
Apparently DTS uses odbc and can not establish the connection despite
Sysadmin rights on both servers. I tried to specify the account sa of
sql server for authentication instead of using windows authentication
but that yields the same result.
Would someone know the solution?
Thank you.Andreas.meyer@.dmc-group.de wrote:
> Hello,
> I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
> 2000. Both belong to the same domain and can see each other without
> problems. A mutual registration of the other sql server in Enterprise
> Manager is no problem.
> One Server's operating system is win2003Server, the other one's is
> Win2000Server.
> In both servers the domain account I use for logging in and for
> authentification purposes is a member of the server's local
> administrators group. And the local administrators have sysadmin rights
> in sql server 2000 via builtin\administrators.
> After some tests I added my windows domain account explicitly as
> sysadmin in both SQL-Servers.
> The security mode is "mixed" (SQL-Login and Windows).
> Trying to transfer a Test database with 1MB space fails. No matter
> whether I use a Transfer Database Task or whether I use the Copy
> Database Wizard (which also uses DTS in the background).
> The Transfer Database Task needs FIVE minutes for the dialog window
> "Transfer Database Properties" to reappear after clicking on the
> tab-card [file locations].
> Below the grid is a green check mark: Files are ready to be moved or
> copied.".
> Below that is a red X: Files on the source have the same name as on the
> destination or there is not enough free disk space on the destination.
> On both servers there is plenty of space (dozens of GB).
> In the end I only get the error description "Unspecified error".
> Doing the same with the Copy Database wizard" in the Grid beside the
> .mdf file and the .ldf file shows the STATUS: OK
> Below, again two error messages:
> Name conflict: Type a new name into the Destination Files fields
> Disk space: Change the destination or free disk space
> At the same time is shown the space needed and available:
> E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
> So I run the job in the wizard immediately and get the following
> errors:
> Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
> Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
> Server]Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
> Step Error code: 80004005
> Step Error Help File:SQLDMO80.hlp
> Step Error Help Context ID:700
> Apparently DTS uses odbc and can not establish the connection despite
> Sysadmin rights on both servers. I tried to specify the account sa of
> sql server for authentication instead of using windows authentication
> but that yields the same result.
> Would someone know the solution?
> Thank you.
>
Save yourself the headache and stop using these wizards for such a
simple task. Simply take a backup of the source database, then restore
that onto the destination server. The syntax for the BACKUP and RESTORE
commands is pretty simple, see Books Online for details.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
of course, I did already.
However, there is so much fuss being made of what sql server 2000 can
do.
Also it is so much stressed in the exams: and dare you you wouldn't
know what the copy database wizard or DTS is able to to and that to use
it is so much easier and surely the best solution when asked for "the
least administrative effort", etc.
Then you try with one of the simplest tasks and in practice it just
fails in an environment where it is truly hard that it wouldn't work.
Yet it doesn't.
Nothing left any more of all the glory...
This is annoying.
Then again, I would like to know the reason for the error message in
odbc.
My impression is: a lot is just marketing but not working, really.
Sincerely
Andreas
Tracy McKibben schrieb:
> Andreas.meyer@.dmc-group.de wrote:
> Save yourself the headache and stop using these wizards for such a
> simple task. Simply take a backup of the source database, then restore
> that onto the destination server. The syntax for the BACKUP and RESTORE
> commands is pretty simple, see Books Online for details.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
2000. Both belong to the same domain and can see each other without
problems. A mutual registration of the other sql server in Enterprise
Manager is no problem.
One Server's operating system is win2003Server, the other one's is
Win2000Server.
In both servers the domain account I use for logging in and for
authentification purposes is a member of the server's local
administrators group. And the local administrators have sysadmin rights
in sql server 2000 via builtin\administrators.
After some tests I added my windows domain account explicitly as
sysadmin in both SQL-Servers.
The security mode is "mixed" (SQL-Login and Windows).
Trying to transfer a Test database with 1MB space fails. No matter
whether I use a Transfer Database Task or whether I use the Copy
Database Wizard (which also uses DTS in the background).
The Transfer Database Task needs FIVE minutes for the dialog window
"Transfer Database Properties" to reappear after clicking on the
tab-card [file locations].
Below the grid is a green check mark: Files are ready to be moved or
copied.".
Below that is a red X: Files on the source have the same name as on the
destination or there is not enough free disk space on the destination.
On both servers there is plenty of space (dozens of GB).
In the end I only get the error description "Unspecified error".
Doing the same with the Copy Database wizard" in the Grid beside the
.mdf file and the .ldf file shows the STATUS: OK
Below, again two error messages:
Name conflict: Type a new name into the Destination Files fields
Disk space: Change the destination or free disk space
At the same time is shown the space needed and available:
E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
So I run the job in the wizard immediately and get the following
errors:
Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
Step Error code: 80004005
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:700
Apparently DTS uses odbc and can not establish the connection despite
Sysadmin rights on both servers. I tried to specify the account sa of
sql server for authentication instead of using windows authentication
but that yields the same result.
Would someone know the solution?
Thank you.Andreas.meyer@.dmc-group.de wrote:
> Hello,
> I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
> 2000. Both belong to the same domain and can see each other without
> problems. A mutual registration of the other sql server in Enterprise
> Manager is no problem.
> One Server's operating system is win2003Server, the other one's is
> Win2000Server.
> In both servers the domain account I use for logging in and for
> authentification purposes is a member of the server's local
> administrators group. And the local administrators have sysadmin rights
> in sql server 2000 via builtin\administrators.
> After some tests I added my windows domain account explicitly as
> sysadmin in both SQL-Servers.
> The security mode is "mixed" (SQL-Login and Windows).
> Trying to transfer a Test database with 1MB space fails. No matter
> whether I use a Transfer Database Task or whether I use the Copy
> Database Wizard (which also uses DTS in the background).
> The Transfer Database Task needs FIVE minutes for the dialog window
> "Transfer Database Properties" to reappear after clicking on the
> tab-card [file locations].
> Below the grid is a green check mark: Files are ready to be moved or
> copied.".
> Below that is a red X: Files on the source have the same name as on the
> destination or there is not enough free disk space on the destination.
> On both servers there is plenty of space (dozens of GB).
> In the end I only get the error description "Unspecified error".
> Doing the same with the Copy Database wizard" in the Grid beside the
> .mdf file and the .ldf file shows the STATUS: OK
> Below, again two error messages:
> Name conflict: Type a new name into the Destination Files fields
> Disk space: Change the destination or free disk space
> At the same time is shown the space needed and available:
> E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
> So I run the job in the wizard immediately and get the following
> errors:
> Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
> Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
> Server]Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
> Step Error code: 80004005
> Step Error Help File:SQLDMO80.hlp
> Step Error Help Context ID:700
> Apparently DTS uses odbc and can not establish the connection despite
> Sysadmin rights on both servers. I tried to specify the account sa of
> sql server for authentication instead of using windows authentication
> but that yields the same result.
> Would someone know the solution?
> Thank you.
>
Save yourself the headache and stop using these wizards for such a
simple task. Simply take a backup of the source database, then restore
that onto the destination server. The syntax for the BACKUP and RESTORE
commands is pretty simple, see Books Online for details.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
of course, I did already.
However, there is so much fuss being made of what sql server 2000 can
do.
Also it is so much stressed in the exams: and dare you you wouldn't
know what the copy database wizard or DTS is able to to and that to use
it is so much easier and surely the best solution when asked for "the
least administrative effort", etc.
Then you try with one of the simplest tasks and in practice it just
fails in an environment where it is truly hard that it wouldn't work.
Yet it doesn't.
Nothing left any more of all the glory...
This is annoying.
Then again, I would like to know the reason for the error message in
odbc.
My impression is: a lot is just marketing but not working, really.
Sincerely
Andreas
Tracy McKibben schrieb:
> Andreas.meyer@.dmc-group.de wrote:
> Save yourself the headache and stop using these wizards for such a
> simple task. Simply take a backup of the source database, then restore
> that onto the destination server. The syntax for the BACKUP and RESTORE
> commands is pretty simple, see Books Online for details.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Copy Database Wizard and DTS Transfer Database Task don't work
Hello,
I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
2000. Both belong to the same domain and can see each other without
problems. A mutual registration of the other sql server in Enterprise
Manager is no problem.
One Server's operating system is win2003Server, the other one's is
Win2000Server.
In both servers the domain account I use for logging in and for
authentification purposes is a member of the server's local
administrators group. And the local administrators have sysadmin rights
in sql server 2000 via builtin\administrators.
After some tests I added my windows domain account explicitly as
sysadmin in both SQL-Servers.
The security mode is "mixed" (SQL-Login and Windows).
Trying to transfer a Test database with 1MB space fails. No matter
whether I use a Transfer Database Task or whether I use the Copy
Database Wizard (which also uses DTS in the background).
The Transfer Database Task needs FIVE minutes for the dialog window
"Transfer Database Properties" to reappear after clicking on the
tab-card [file locations].
Below the grid is a green check mark: Files are ready to be moved or
copied.".
Below that is a red X: Files on the source have the same name as on the
destination or there is not enough free disk space on the destination.
On both servers there is plenty of space (dozens of GB).
In the end I only get the error description "Unspecified error".
Doing the same with the Copy Database wizard" in the Grid beside the
.mdf file and the .ldf file shows the STATUS: OK
Below, again two error messages:
Name conflict: Type a new name into the Destination Files fields
Disk space: Change the destination or free disk space
At the same time is shown the space needed and available:
E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
So I run the job in the wizard immediately and get the following
errors:
Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
Step Error code: 80004005
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:700
Apparently DTS uses odbc and can not establish the connection despite
Sysadmin rights on both servers. I tried to specify the account sa of
sql server for authentication instead of using windows authentication
but that yields the same result.
Would someone know the solution?
Thank you.Andreas.meyer@.dmc-group.de wrote:
> Hello,
> I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
> 2000. Both belong to the same domain and can see each other without
> problems. A mutual registration of the other sql server in Enterprise
> Manager is no problem.
> One Server's operating system is win2003Server, the other one's is
> Win2000Server.
> In both servers the domain account I use for logging in and for
> authentification purposes is a member of the server's local
> administrators group. And the local administrators have sysadmin rights
> in sql server 2000 via builtin\administrators.
> After some tests I added my windows domain account explicitly as
> sysadmin in both SQL-Servers.
> The security mode is "mixed" (SQL-Login and Windows).
> Trying to transfer a Test database with 1MB space fails. No matter
> whether I use a Transfer Database Task or whether I use the Copy
> Database Wizard (which also uses DTS in the background).
> The Transfer Database Task needs FIVE minutes for the dialog window
> "Transfer Database Properties" to reappear after clicking on the
> tab-card [file locations].
> Below the grid is a green check mark: Files are ready to be moved or
> copied.".
> Below that is a red X: Files on the source have the same name as on the
> destination or there is not enough free disk space on the destination.
> On both servers there is plenty of space (dozens of GB).
> In the end I only get the error description "Unspecified error".
> Doing the same with the Copy Database wizard" in the Grid beside the
> .mdf file and the .ldf file shows the STATUS: OK
> Below, again two error messages:
> Name conflict: Type a new name into the Destination Files fields
> Disk space: Change the destination or free disk space
> At the same time is shown the space needed and available:
> E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
> So I run the job in the wizard immediately and get the following
> errors:
> Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
> Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
> Server]Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
> Step Error code: 80004005
> Step Error Help File:SQLDMO80.hlp
> Step Error Help Context ID:700
> Apparently DTS uses odbc and can not establish the connection despite
> Sysadmin rights on both servers. I tried to specify the account sa of
> sql server for authentication instead of using windows authentication
> but that yields the same result.
> Would someone know the solution?
> Thank you.
>
Save yourself the headache and stop using these wizards for such a
simple task. Simply take a backup of the source database, then restore
that onto the destination server. The syntax for the BACKUP and RESTORE
commands is pretty simple, see Books Online for details.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
of course, I did already.
However, there is so much fuss being made of what sql server 2000 can
do.
Also it is so much stressed in the exams: and dare you you wouldn't
know what the copy database wizard or DTS is able to to and that to use
it is so much easier and surely the best solution when asked for "the
least administrative effort", etc.
Then you try with one of the simplest tasks and in practice it just
fails in an environment where it is truly hard that it wouldn't work.
Yet it doesn't.
Nothing left any more of all the glory...
This is annoying.
Then again, I would like to know the reason for the error message in
odbc.
My impression is: a lot is just marketing but not working, really.
Sincerely
Andreas
Tracy McKibben schrieb:
> Andreas.meyer@.dmc-group.de wrote:
> > Hello,
> > I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
> > 2000. Both belong to the same domain and can see each other without
> > problems. A mutual registration of the other sql server in Enterprise
> > Manager is no problem.
> > One Server's operating system is win2003Server, the other one's is
> > Win2000Server.
> > In both servers the domain account I use for logging in and for
> > authentification purposes is a member of the server's local
> > administrators group. And the local administrators have sysadmin rights
> > in sql server 2000 via builtin\administrators.
> > After some tests I added my windows domain account explicitly as
> > sysadmin in both SQL-Servers.
> > The security mode is "mixed" (SQL-Login and Windows).
> >
> > Trying to transfer a Test database with 1MB space fails. No matter
> > whether I use a Transfer Database Task or whether I use the Copy
> > Database Wizard (which also uses DTS in the background).
> > The Transfer Database Task needs FIVE minutes for the dialog window
> > "Transfer Database Properties" to reappear after clicking on the
> > tab-card [file locations].
> > Below the grid is a green check mark: Files are ready to be moved or
> > copied.".
> > Below that is a red X: Files on the source have the same name as on the
> > destination or there is not enough free disk space on the destination.
> >
> > On both servers there is plenty of space (dozens of GB).
> > In the end I only get the error description "Unspecified error".
> >
> > Doing the same with the Copy Database wizard" in the Grid beside the
> > .mdf file and the .ldf file shows the STATUS: OK
> > Below, again two error messages:
> >
> > Name conflict: Type a new name into the Destination Files fields
> > Disk space: Change the destination or free disk space
> >
> > At the same time is shown the space needed and available:
> > E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
> >
> > So I run the job in the wizard immediately and get the following
> > errors:
> >
> > Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
> > Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
> > Server]Login failed for user '(null)'. Reason: Not associated with a
> > trusted SQL Server connection.
> > Step Error code: 80004005
> > Step Error Help File:SQLDMO80.hlp
> > Step Error Help Context ID:700
> >
> > Apparently DTS uses odbc and can not establish the connection despite
> > Sysadmin rights on both servers. I tried to specify the account sa of
> > sql server for authentication instead of using windows authentication
> > but that yields the same result.
> > Would someone know the solution?
> >
> > Thank you.
> >
> Save yourself the headache and stop using these wizards for such a
> simple task. Simply take a backup of the source database, then restore
> that onto the destination server. The syntax for the BACKUP and RESTORE
> commands is pretty simple, see Books Online for details.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
2000. Both belong to the same domain and can see each other without
problems. A mutual registration of the other sql server in Enterprise
Manager is no problem.
One Server's operating system is win2003Server, the other one's is
Win2000Server.
In both servers the domain account I use for logging in and for
authentification purposes is a member of the server's local
administrators group. And the local administrators have sysadmin rights
in sql server 2000 via builtin\administrators.
After some tests I added my windows domain account explicitly as
sysadmin in both SQL-Servers.
The security mode is "mixed" (SQL-Login and Windows).
Trying to transfer a Test database with 1MB space fails. No matter
whether I use a Transfer Database Task or whether I use the Copy
Database Wizard (which also uses DTS in the background).
The Transfer Database Task needs FIVE minutes for the dialog window
"Transfer Database Properties" to reappear after clicking on the
tab-card [file locations].
Below the grid is a green check mark: Files are ready to be moved or
copied.".
Below that is a red X: Files on the source have the same name as on the
destination or there is not enough free disk space on the destination.
On both servers there is plenty of space (dozens of GB).
In the end I only get the error description "Unspecified error".
Doing the same with the Copy Database wizard" in the Grid beside the
.mdf file and the .ldf file shows the STATUS: OK
Below, again two error messages:
Name conflict: Type a new name into the Destination Files fields
Disk space: Change the destination or free disk space
At the same time is shown the space needed and available:
E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
So I run the job in the wizard immediately and get the following
errors:
Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.
Step Error code: 80004005
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:700
Apparently DTS uses odbc and can not establish the connection despite
Sysadmin rights on both servers. I tried to specify the account sa of
sql server for authentication instead of using windows authentication
but that yields the same result.
Would someone know the solution?
Thank you.Andreas.meyer@.dmc-group.de wrote:
> Hello,
> I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
> 2000. Both belong to the same domain and can see each other without
> problems. A mutual registration of the other sql server in Enterprise
> Manager is no problem.
> One Server's operating system is win2003Server, the other one's is
> Win2000Server.
> In both servers the domain account I use for logging in and for
> authentification purposes is a member of the server's local
> administrators group. And the local administrators have sysadmin rights
> in sql server 2000 via builtin\administrators.
> After some tests I added my windows domain account explicitly as
> sysadmin in both SQL-Servers.
> The security mode is "mixed" (SQL-Login and Windows).
> Trying to transfer a Test database with 1MB space fails. No matter
> whether I use a Transfer Database Task or whether I use the Copy
> Database Wizard (which also uses DTS in the background).
> The Transfer Database Task needs FIVE minutes for the dialog window
> "Transfer Database Properties" to reappear after clicking on the
> tab-card [file locations].
> Below the grid is a green check mark: Files are ready to be moved or
> copied.".
> Below that is a red X: Files on the source have the same name as on the
> destination or there is not enough free disk space on the destination.
> On both servers there is plenty of space (dozens of GB).
> In the end I only get the error description "Unspecified error".
> Doing the same with the Copy Database wizard" in the Grid beside the
> .mdf file and the .ldf file shows the STATUS: OK
> Below, again two error messages:
> Name conflict: Type a new name into the Destination Files fields
> Disk space: Change the destination or free disk space
> At the same time is shown the space needed and available:
> E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
> So I run the job in the wizard immediately and get the following
> errors:
> Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
> Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
> Server]Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
> Step Error code: 80004005
> Step Error Help File:SQLDMO80.hlp
> Step Error Help Context ID:700
> Apparently DTS uses odbc and can not establish the connection despite
> Sysadmin rights on both servers. I tried to specify the account sa of
> sql server for authentication instead of using windows authentication
> but that yields the same result.
> Would someone know the solution?
> Thank you.
>
Save yourself the headache and stop using these wizards for such a
simple task. Simply take a backup of the source database, then restore
that onto the destination server. The syntax for the BACKUP and RESTORE
commands is pretty simple, see Books Online for details.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
of course, I did already.
However, there is so much fuss being made of what sql server 2000 can
do.
Also it is so much stressed in the exams: and dare you you wouldn't
know what the copy database wizard or DTS is able to to and that to use
it is so much easier and surely the best solution when asked for "the
least administrative effort", etc.
Then you try with one of the simplest tasks and in practice it just
fails in an environment where it is truly hard that it wouldn't work.
Yet it doesn't.
Nothing left any more of all the glory...
This is annoying.
Then again, I would like to know the reason for the error message in
odbc.
My impression is: a lot is just marketing but not working, really.
Sincerely
Andreas
Tracy McKibben schrieb:
> Andreas.meyer@.dmc-group.de wrote:
> > Hello,
> > I work with two SQL-Server 2000 computers. Both hav SP4 for SQL Server
> > 2000. Both belong to the same domain and can see each other without
> > problems. A mutual registration of the other sql server in Enterprise
> > Manager is no problem.
> > One Server's operating system is win2003Server, the other one's is
> > Win2000Server.
> > In both servers the domain account I use for logging in and for
> > authentification purposes is a member of the server's local
> > administrators group. And the local administrators have sysadmin rights
> > in sql server 2000 via builtin\administrators.
> > After some tests I added my windows domain account explicitly as
> > sysadmin in both SQL-Servers.
> > The security mode is "mixed" (SQL-Login and Windows).
> >
> > Trying to transfer a Test database with 1MB space fails. No matter
> > whether I use a Transfer Database Task or whether I use the Copy
> > Database Wizard (which also uses DTS in the background).
> > The Transfer Database Task needs FIVE minutes for the dialog window
> > "Transfer Database Properties" to reappear after clicking on the
> > tab-card [file locations].
> > Below the grid is a green check mark: Files are ready to be moved or
> > copied.".
> > Below that is a red X: Files on the source have the same name as on the
> > destination or there is not enough free disk space on the destination.
> >
> > On both servers there is plenty of space (dozens of GB).
> > In the end I only get the error description "Unspecified error".
> >
> > Doing the same with the Copy Database wizard" in the Grid beside the
> > .mdf file and the .ldf file shows the STATUS: OK
> > Below, again two error messages:
> >
> > Name conflict: Type a new name into the Destination Files fields
> > Disk space: Change the destination or free disk space
> >
> > At the same time is shown the space needed and available:
> > E: Available Space: 56956,00 MB, Required Space: 2,00 MB.
> >
> > So I run the job in the wizard immediately and get the following
> > errors:
> >
> > Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 28000)
> > Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL
> > Server]Login failed for user '(null)'. Reason: Not associated with a
> > trusted SQL Server connection.
> > Step Error code: 80004005
> > Step Error Help File:SQLDMO80.hlp
> > Step Error Help Context ID:700
> >
> > Apparently DTS uses odbc and can not establish the connection despite
> > Sysadmin rights on both servers. I tried to specify the account sa of
> > sql server for authentication instead of using windows authentication
> > but that yields the same result.
> > Would someone know the solution?
> >
> > Thank you.
> >
> Save yourself the headache and stop using these wizards for such a
> simple task. Simply take a backup of the source database, then restore
> that onto the destination server. The syntax for the BACKUP and RESTORE
> commands is pretty simple, see Books Online for details.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Tuesday, March 20, 2012
Copy Database Wizard
Using SQL 2000 SP3a on Windows 2000 Server, Active Directory domain. I want
to copy a database from a development server to a production server. But
when I run the Copy Database Wizard, it says the SQL server Service can't
run under the local system account. I've searched MSDN and couldn't find
anything on this subject. Do I need to enable the Interact with the Desktop
option? Or do I need to create a Domain User for both servers to run under?
Or local users on each machine with some extra priveleges?Have a look at the "Permissions to Copy the Files" section in
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274463
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:e8hQmUurDHA.3748@.TK2MSFTNGP11.phx.gbl...
Using SQL 2000 SP3a on Windows 2000 Server, Active Directory domain. I want
to copy a database from a development server to a production server. But
when I run the Copy Database Wizard, it says the SQL server Service can't
run under the local system account. I've searched MSDN and couldn't find
anything on this subject. Do I need to enable the Interact with the Desktop
option? Or do I need to create a Domain User for both servers to run under?
Or local users on each machine with some extra priveleges?
to copy a database from a development server to a production server. But
when I run the Copy Database Wizard, it says the SQL server Service can't
run under the local system account. I've searched MSDN and couldn't find
anything on this subject. Do I need to enable the Interact with the Desktop
option? Or do I need to create a Domain User for both servers to run under?
Or local users on each machine with some extra priveleges?Have a look at the "Permissions to Copy the Files" section in
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274463
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:e8hQmUurDHA.3748@.TK2MSFTNGP11.phx.gbl...
Using SQL 2000 SP3a on Windows 2000 Server, Active Directory domain. I want
to copy a database from a development server to a production server. But
when I run the Copy Database Wizard, it says the SQL server Service can't
run under the local system account. I've searched MSDN and couldn't find
anything on this subject. Do I need to enable the Interact with the Desktop
option? Or do I need to create a Domain User for both servers to run under?
Or local users on each machine with some extra priveleges?
Copy Database Wizard
We have member SQL servers in a workgroup, running in a netware environment.
We do not have a domain. The wizard fails when I try to copy a database f
rom one server to another. What's the solution or workaround?
Thank you.Part of the process for the Copy Database Wizard involves the SQL Server
startup account on the destination accessing a mapped drive on the source
machine. If this account cannot access a mapped drive the Copy Database
Wizard will fail.
Rand
This posting is provided "as is" with no warranties and confers no rights.
We do not have a domain. The wizard fails when I try to copy a database f
rom one server to another. What's the solution or workaround?
Thank you.Part of the process for the Copy Database Wizard involves the SQL Server
startup account on the destination accessing a mapped drive on the source
machine. If this account cannot access a mapped drive the Copy Database
Wizard will fail.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Monday, March 19, 2012
Copy database from remote server to local?
My domain host hosts my MS SQL 2000 database. I am able to connect to it
from my workstation using the MS SQL Server Management Studio Express
application. I want to copy from the remote server, modify it, and upload it
back to my domain host.
I don't see any method of copying the remote database to my local machine.
Help?Hi,
u can backup the database to the remote server or mirror the backup
to remote location.
u should have permission on the shared folder of the remote server.
for mirroring see help
HTH
from
Doller|||Hi,
u can backup the database to the remote server
u should have permission on the shared folder of the remote server.
HTH
from
Doller|||"doller" <sufianarif@.gmail.com> wrote in message
news:1145437778.697809.321740@.z34g2000cwc.googlegroups.com...
> Hi,
> u can backup the database to the remote server
> u should have permission on the shared folder of the remote server.
I am able to generate the backup on the remote server, but I have no access
to actually download the backup once generated.
I do have a local MS SQL 2005 server, but I can't see any method to backup
from the remote server to the local server.|||BACKUP is executed by SQL Server, so the backup file will be generated by SQ
L Server. Either direct
the file to the desired location when you do the backup (UNC path) or do it
locally and then grab
the file (COPY, FTP etc).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Noozer" <dont.spam@.me.here> wrote in message news:6SC1g.41524$P01.35165@.pd7tw3no...eagreen">
> "doller" <sufianarif@.gmail.com> wrote in message
> news:1145437778.697809.321740@.z34g2000cwc.googlegroups.com...
> I am able to generate the backup on the remote server, but I have no acces
s to actually download
> the backup once generated.
> I do have a local MS SQL 2005 server, but I can't see any method to backup
from the remote server
> to the local server.
>
>
from my workstation using the MS SQL Server Management Studio Express
application. I want to copy from the remote server, modify it, and upload it
back to my domain host.
I don't see any method of copying the remote database to my local machine.
Help?Hi,
u can backup the database to the remote server or mirror the backup
to remote location.
u should have permission on the shared folder of the remote server.
for mirroring see help
HTH
from
Doller|||Hi,
u can backup the database to the remote server
u should have permission on the shared folder of the remote server.
HTH
from
Doller|||"doller" <sufianarif@.gmail.com> wrote in message
news:1145437778.697809.321740@.z34g2000cwc.googlegroups.com...
> Hi,
> u can backup the database to the remote server
> u should have permission on the shared folder of the remote server.
I am able to generate the backup on the remote server, but I have no access
to actually download the backup once generated.
I do have a local MS SQL 2005 server, but I can't see any method to backup
from the remote server to the local server.|||BACKUP is executed by SQL Server, so the backup file will be generated by SQ
L Server. Either direct
the file to the desired location when you do the backup (UNC path) or do it
locally and then grab
the file (COPY, FTP etc).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Noozer" <dont.spam@.me.here> wrote in message news:6SC1g.41524$P01.35165@.pd7tw3no...eagreen">
> "doller" <sufianarif@.gmail.com> wrote in message
> news:1145437778.697809.321740@.z34g2000cwc.googlegroups.com...
> I am able to generate the backup on the remote server, but I have no acces
s to actually download
> the backup once generated.
> I do have a local MS SQL 2005 server, but I can't see any method to backup
from the remote server
> to the local server.
>
>
Copy database from remote server to local?
My domain host hosts my MS SQL 2000 database. I am able to connect to it
from my workstation using the MS SQL Server Management Studio Express
application. I want to copy from the remote server, modify it, and upload it
back to my domain host.
I don't see any method of copying the remote database to my local machine.
Help?Hi,
u can backup the database to the remote server or mirror the backup
to remote location.
u should have permission on the shared folder of the remote server.
for mirroring see help
HTH
from
Doller|||Hi,
u can backup the database to the remote server
u should have permission on the shared folder of the remote server.
HTH
from
Doller|||"doller" <sufianarif@.gmail.com> wrote in message
news:1145437778.697809.321740@.z34g2000cwc.googlegroups.com...
> Hi,
> u can backup the database to the remote server
> u should have permission on the shared folder of the remote server.
I am able to generate the backup on the remote server, but I have no access
to actually download the backup once generated.
I do have a local MS SQL 2005 server, but I can't see any method to backup
from the remote server to the local server.|||BACKUP is executed by SQL Server, so the backup file will be generated by SQL Server. Either direct
the file to the desired location when you do the backup (UNC path) or do it locally and then grab
the file (COPY, FTP etc).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Noozer" <dont.spam@.me.here> wrote in message news:6SC1g.41524$P01.35165@.pd7tw3no...
> "doller" <sufianarif@.gmail.com> wrote in message
> news:1145437778.697809.321740@.z34g2000cwc.googlegroups.com...
>> Hi,
>> u can backup the database to the remote server
>> u should have permission on the shared folder of the remote server.
> I am able to generate the backup on the remote server, but I have no access to actually download
> the backup once generated.
> I do have a local MS SQL 2005 server, but I can't see any method to backup from the remote server
> to the local server.
>
>
from my workstation using the MS SQL Server Management Studio Express
application. I want to copy from the remote server, modify it, and upload it
back to my domain host.
I don't see any method of copying the remote database to my local machine.
Help?Hi,
u can backup the database to the remote server or mirror the backup
to remote location.
u should have permission on the shared folder of the remote server.
for mirroring see help
HTH
from
Doller|||Hi,
u can backup the database to the remote server
u should have permission on the shared folder of the remote server.
HTH
from
Doller|||"doller" <sufianarif@.gmail.com> wrote in message
news:1145437778.697809.321740@.z34g2000cwc.googlegroups.com...
> Hi,
> u can backup the database to the remote server
> u should have permission on the shared folder of the remote server.
I am able to generate the backup on the remote server, but I have no access
to actually download the backup once generated.
I do have a local MS SQL 2005 server, but I can't see any method to backup
from the remote server to the local server.|||BACKUP is executed by SQL Server, so the backup file will be generated by SQL Server. Either direct
the file to the desired location when you do the backup (UNC path) or do it locally and then grab
the file (COPY, FTP etc).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Noozer" <dont.spam@.me.here> wrote in message news:6SC1g.41524$P01.35165@.pd7tw3no...
> "doller" <sufianarif@.gmail.com> wrote in message
> news:1145437778.697809.321740@.z34g2000cwc.googlegroups.com...
>> Hi,
>> u can backup the database to the remote server
>> u should have permission on the shared folder of the remote server.
> I am able to generate the backup on the remote server, but I have no access to actually download
> the backup once generated.
> I do have a local MS SQL 2005 server, but I can't see any method to backup from the remote server
> to the local server.
>
>
Copy database from one server to other
We had two physical SQL servers and copying one database using the wizard to
the other sqlserver was easy because both services used the same domain
account. Now i will have to copy databases from one server to another
outside the domain. This means they will have seperate logins for the
sqlserver service. how can i then use the copy database wizard? It fails
because it can't create a file on the ditination server'
does this mean i have to use log shipping or use a script and then copy just
data'
thanks.You can use backup/restore or sp_attachdb, sp_detachdb. You will have to
manually script out the logins. See this page for more info:
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Richard K." <google@.walkersca.com> wrote in message
news:uCR%23ry98DHA.3404@.TK2MSFTNGP09.phx.gbl...
> We had two physical SQL servers and copying one database using the wizard
to
> the other sqlserver was easy because both services used the same domain
> account. Now i will have to copy databases from one server to another
> outside the domain. This means they will have seperate logins for the
> sqlserver service. how can i then use the copy database wizard? It fails
> because it can't create a file on the ditination server'
> does this mean i have to use log shipping or use a script and then copy
just
> data'
> thanks.
>
the other sqlserver was easy because both services used the same domain
account. Now i will have to copy databases from one server to another
outside the domain. This means they will have seperate logins for the
sqlserver service. how can i then use the copy database wizard? It fails
because it can't create a file on the ditination server'
does this mean i have to use log shipping or use a script and then copy just
data'
thanks.You can use backup/restore or sp_attachdb, sp_detachdb. You will have to
manually script out the logins. See this page for more info:
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Richard K." <google@.walkersca.com> wrote in message
news:uCR%23ry98DHA.3404@.TK2MSFTNGP09.phx.gbl...
> We had two physical SQL servers and copying one database using the wizard
to
> the other sqlserver was easy because both services used the same domain
> account. Now i will have to copy databases from one server to another
> outside the domain. This means they will have seperate logins for the
> sqlserver service. how can i then use the copy database wizard? It fails
> because it can't create a file on the ditination server'
> does this mean i have to use log shipping or use a script and then copy
just
> data'
> thanks.
>
Thursday, March 8, 2012
Copy data to another server via XML?
Hello...
I have to transfer/copy data from our SQL 2005 server to another server that
is NOT part of our domain. I was figuing to use XML to do this...but we hav
e
some image data types in some of our tables and I cannot figure out how to
include that data in the XML.
Does anyone know of a way to do this..or an article explaining it?
thanks for any help
- willHello dw,
If you are using SQL Server 2005, take a look at Integration Services.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Thanks for the advice. I just found out that the customer requirements do
not include a need for image/binary data...so I am now thinking of using the
HTTP Endpoints stuff...not really sure as I don't know too much about it
yet. But it looks promising.
"Kent Tegels" wrote:
> Hello dw,
> If you are using SQL Server 2005, take a look at Integration Services.
> Thanks!
> Kent Tegels
> DevelopMentor
> http://staff.develop.com/ktegels/
>
>|||dw wrote:
> Thanks for the advice. I just found out that the customer requirements do
> not include a need for image/binary data...so I am now thinking of using t
he
> HTTP Endpoints stuff...not really sure as I don't know too much about it
> yet. But it looks promising.
For the record, XML itself is designed for text information, so it
cannot hold binary (image) data direct: it has to be encoded into
text characters first or referenced externally (like HTML).
But as Kent has pointed out, suppliers provide built-in ways to do
this for you.
///Peter
--
XML FAQ: http://xml.silmaril.ie/
> "Kent Tegels" wrote:
>
I have to transfer/copy data from our SQL 2005 server to another server that
is NOT part of our domain. I was figuing to use XML to do this...but we hav
e
some image data types in some of our tables and I cannot figure out how to
include that data in the XML.
Does anyone know of a way to do this..or an article explaining it?
thanks for any help
- willHello dw,
If you are using SQL Server 2005, take a look at Integration Services.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Thanks for the advice. I just found out that the customer requirements do
not include a need for image/binary data...so I am now thinking of using the
HTTP Endpoints stuff...not really sure as I don't know too much about it
yet. But it looks promising.
"Kent Tegels" wrote:
> Hello dw,
> If you are using SQL Server 2005, take a look at Integration Services.
> Thanks!
> Kent Tegels
> DevelopMentor
> http://staff.develop.com/ktegels/
>
>|||dw wrote:
> Thanks for the advice. I just found out that the customer requirements do
> not include a need for image/binary data...so I am now thinking of using t
he
> HTTP Endpoints stuff...not really sure as I don't know too much about it
> yet. But it looks promising.
For the record, XML itself is designed for text information, so it
cannot hold binary (image) data direct: it has to be encoded into
text characters first or referenced externally (like HTML).
But as Kent has pointed out, suppliers provide built-in ways to do
this for you.
///Peter
--
XML FAQ: http://xml.silmaril.ie/
> "Kent Tegels" wrote:
>
Subscribe to:
Posts (Atom)