Hi.
Is there any simple way of copying all of the ssis packages between two
servers?
I have just installed sql 2005 on a new, better equipped machine and I have
to move there all the data. Including ssis of course. There are about 40-50
packages to do (stored in the database, not in filesystem) and I hope there
is a better way than just to import packages (one by one) to a text file
and export them to another server.
BTW, I'm going to copy the job definitions as well, there are about 20 jobs
defined on the server, is there any handy way of doing this? Any hints?
PLTry backing up and restoring MSDB and changing the appropriate fields.
We do this with jobs every week to keep 2 servers in sync and this is what
we use to bring the jobs up to date. I would imagine that it could be just
as easy for SSIS packages, though I haven't tried it officially.
UPDATE sysjobs
SET originating_server = 'MyServer'
So just run that on the new server once you have MSDB restored on there and
you should be OK. And just check the SSIS tables to discover similar entrie
s
that may need to be changed.
"Piotr Lipski" wrote:
> Hi.
> Is there any simple way of copying all of the ssis packages between two
> servers?
> I have just installed sql 2005 on a new, better equipped machine and I hav
e
> to move there all the data. Including ssis of course. There are about 40-5
0
> packages to do (stored in the database, not in filesystem) and I hope ther
e
> is a better way than just to import packages (one by one) to a text file
> and export them to another server.
> BTW, I'm going to copy the job definitions as well, there are about 20 job
s
> defined on the server, is there any handy way of doing this? Any hints?
> --
> PL
>|||Sean McCown wrote:
> Try backing up and restoring MSDB and changing the appropriate fields.
> We do this with jobs every week to keep 2 servers in sync and this is what
> we use to bring the jobs up to date. I would imagine that it could be jus
t
> as easy for SSIS packages, though I haven't tried it officially.
> UPDATE sysjobs
> SET originating_server = 'MyServer'
> So just run that on the new server once you have MSDB restored on there an
d
> you should be OK. And just check the SSIS tables to discover similar entr
ies
> that may need to be changed.
Right. But how to restore the msdb database? When I try to do it from
SMS (right click on database -> tasks -> restore) I get failure message
"Exclusive access could not be obtained because the database is in
use.", which makes sense but does not resolve the problem. There is also
no option to go off-line or detach for that database.
Should I just replace the msdb datafiles (mdf/ldf) with the ones from
'old' server?
PL|||OK, there are a couple things here...
first, to restore MSDB just startup SQL with -T3608 and -m. 3608 prevents
startup of all system DBs except master. -m is single-user mode. So you
should now be able to restore MSDB with no problem. If you're doing it from
the command line, then use -c.
Second, You can always just setup a linked server and copy the raw data over
without restoring.
Good luck.
"Piotr Lipski" wrote:
> Sean McCown wrote:
> Right. But how to restore the msdb database? When I try to do it from
> SMS (right click on database -> tasks -> restore) I get failure message
> "Exclusive access could not be obtained because the database is in
> use.", which makes sense but does not resolve the problem. There is also
> no option to go off-line or detach for that database.
> Should I just replace the msdb datafiles (mdf/ldf) with the ones from
> 'old' server?
> --
> PL
>
Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts
Thursday, March 29, 2012
copy many ssis packages between servers
Hi.
Is there any simple way of copying all of the ssis packages between two
servers?
I have just installed sql 2005 on a new, better equipped machine and I have
to move there all the data. Including ssis of course. There are about 40-50
packages to do (stored in the database, not in filesystem) and I hope there
is a better way than just to import packages (one by one) to a text file
and export them to another server.
BTW, I'm going to copy the job definitions as well, there are about 20 jobs
defined on the server, is there any handy way of doing this? Any hints?
--
PLTry backing up and restoring MSDB and changing the appropriate fields.
We do this with jobs every week to keep 2 servers in sync and this is what
we use to bring the jobs up to date. I would imagine that it could be just
as easy for SSIS packages, though I haven't tried it officially.
UPDATE sysjobs
SET originating_server = 'MyServer'
So just run that on the new server once you have MSDB restored on there and
you should be OK. And just check the SSIS tables to discover similar entries
that may need to be changed.
"Piotr Lipski" wrote:
> Hi.
> Is there any simple way of copying all of the ssis packages between two
> servers?
> I have just installed sql 2005 on a new, better equipped machine and I have
> to move there all the data. Including ssis of course. There are about 40-50
> packages to do (stored in the database, not in filesystem) and I hope there
> is a better way than just to import packages (one by one) to a text file
> and export them to another server.
> BTW, I'm going to copy the job definitions as well, there are about 20 jobs
> defined on the server, is there any handy way of doing this? Any hints?
> --
> PL
>|||Sean McCown wrote:
> Try backing up and restoring MSDB and changing the appropriate fields.
> We do this with jobs every week to keep 2 servers in sync and this is what
> we use to bring the jobs up to date. I would imagine that it could be just
> as easy for SSIS packages, though I haven't tried it officially.
> UPDATE sysjobs
> SET originating_server = 'MyServer'
> So just run that on the new server once you have MSDB restored on there and
> you should be OK. And just check the SSIS tables to discover similar entries
> that may need to be changed.
Right. But how to restore the msdb database? When I try to do it from
SMS (right click on database -> tasks -> restore) I get failure message
"Exclusive access could not be obtained because the database is in
use.", which makes sense but does not resolve the problem. There is also
no option to go off-line or detach for that database.
Should I just replace the msdb datafiles (mdf/ldf) with the ones from
'old' server?
--
PL|||OK, there are a couple things here...
first, to restore MSDB just startup SQL with -T3608 and -m. 3608 prevents
startup of all system DBs except master. -m is single-user mode. So you
should now be able to restore MSDB with no problem. If you're doing it from
the command line, then use -c.
Second, You can always just setup a linked server and copy the raw data over
without restoring.
Good luck.
"Piotr Lipski" wrote:
> Sean McCown wrote:
> > Try backing up and restoring MSDB and changing the appropriate fields.
> > We do this with jobs every week to keep 2 servers in sync and this is what
> > we use to bring the jobs up to date. I would imagine that it could be just
> > as easy for SSIS packages, though I haven't tried it officially.
> >
> > UPDATE sysjobs
> > SET originating_server = 'MyServer'
> >
> > So just run that on the new server once you have MSDB restored on there and
> > you should be OK. And just check the SSIS tables to discover similar entries
> > that may need to be changed.
> Right. But how to restore the msdb database? When I try to do it from
> SMS (right click on database -> tasks -> restore) I get failure message
> "Exclusive access could not be obtained because the database is in
> use.", which makes sense but does not resolve the problem. There is also
> no option to go off-line or detach for that database.
> Should I just replace the msdb datafiles (mdf/ldf) with the ones from
> 'old' server?
> --
> PL
>
Is there any simple way of copying all of the ssis packages between two
servers?
I have just installed sql 2005 on a new, better equipped machine and I have
to move there all the data. Including ssis of course. There are about 40-50
packages to do (stored in the database, not in filesystem) and I hope there
is a better way than just to import packages (one by one) to a text file
and export them to another server.
BTW, I'm going to copy the job definitions as well, there are about 20 jobs
defined on the server, is there any handy way of doing this? Any hints?
--
PLTry backing up and restoring MSDB and changing the appropriate fields.
We do this with jobs every week to keep 2 servers in sync and this is what
we use to bring the jobs up to date. I would imagine that it could be just
as easy for SSIS packages, though I haven't tried it officially.
UPDATE sysjobs
SET originating_server = 'MyServer'
So just run that on the new server once you have MSDB restored on there and
you should be OK. And just check the SSIS tables to discover similar entries
that may need to be changed.
"Piotr Lipski" wrote:
> Hi.
> Is there any simple way of copying all of the ssis packages between two
> servers?
> I have just installed sql 2005 on a new, better equipped machine and I have
> to move there all the data. Including ssis of course. There are about 40-50
> packages to do (stored in the database, not in filesystem) and I hope there
> is a better way than just to import packages (one by one) to a text file
> and export them to another server.
> BTW, I'm going to copy the job definitions as well, there are about 20 jobs
> defined on the server, is there any handy way of doing this? Any hints?
> --
> PL
>|||Sean McCown wrote:
> Try backing up and restoring MSDB and changing the appropriate fields.
> We do this with jobs every week to keep 2 servers in sync and this is what
> we use to bring the jobs up to date. I would imagine that it could be just
> as easy for SSIS packages, though I haven't tried it officially.
> UPDATE sysjobs
> SET originating_server = 'MyServer'
> So just run that on the new server once you have MSDB restored on there and
> you should be OK. And just check the SSIS tables to discover similar entries
> that may need to be changed.
Right. But how to restore the msdb database? When I try to do it from
SMS (right click on database -> tasks -> restore) I get failure message
"Exclusive access could not be obtained because the database is in
use.", which makes sense but does not resolve the problem. There is also
no option to go off-line or detach for that database.
Should I just replace the msdb datafiles (mdf/ldf) with the ones from
'old' server?
--
PL|||OK, there are a couple things here...
first, to restore MSDB just startup SQL with -T3608 and -m. 3608 prevents
startup of all system DBs except master. -m is single-user mode. So you
should now be able to restore MSDB with no problem. If you're doing it from
the command line, then use -c.
Second, You can always just setup a linked server and copy the raw data over
without restoring.
Good luck.
"Piotr Lipski" wrote:
> Sean McCown wrote:
> > Try backing up and restoring MSDB and changing the appropriate fields.
> > We do this with jobs every week to keep 2 servers in sync and this is what
> > we use to bring the jobs up to date. I would imagine that it could be just
> > as easy for SSIS packages, though I haven't tried it officially.
> >
> > UPDATE sysjobs
> > SET originating_server = 'MyServer'
> >
> > So just run that on the new server once you have MSDB restored on there and
> > you should be OK. And just check the SSIS tables to discover similar entries
> > that may need to be changed.
> Right. But how to restore the msdb database? When I try to do it from
> SMS (right click on database -> tasks -> restore) I get failure message
> "Exclusive access could not be obtained because the database is in
> use.", which makes sense but does not resolve the problem. There is also
> no option to go off-line or detach for that database.
> Should I just replace the msdb datafiles (mdf/ldf) with the ones from
> 'old' server?
> --
> PL
>
copy many ssis packages between servers
Hi.
Is there any simple way of copying all of the ssis packages between two
servers?
I have just installed sql 2005 on a new, better equipped machine and I have
to move there all the data. Including ssis of course. There are about 40-50
packages to do (stored in the database, not in filesystem) and I hope there
is a better way than just to import packages (one by one) to a text file
and export them to another server.
BTW, I'm going to copy the job definitions as well, there are about 20 jobs
defined on the server, is there any handy way of doing this? Any hints?
PL
Try backing up and restoring MSDB and changing the appropriate fields.
We do this with jobs every week to keep 2 servers in sync and this is what
we use to bring the jobs up to date. I would imagine that it could be just
as easy for SSIS packages, though I haven't tried it officially.
UPDATE sysjobs
SET originating_server = 'MyServer'
So just run that on the new server once you have MSDB restored on there and
you should be OK. And just check the SSIS tables to discover similar entries
that may need to be changed.
"Piotr Lipski" wrote:
> Hi.
> Is there any simple way of copying all of the ssis packages between two
> servers?
> I have just installed sql 2005 on a new, better equipped machine and I have
> to move there all the data. Including ssis of course. There are about 40-50
> packages to do (stored in the database, not in filesystem) and I hope there
> is a better way than just to import packages (one by one) to a text file
> and export them to another server.
> BTW, I'm going to copy the job definitions as well, there are about 20 jobs
> defined on the server, is there any handy way of doing this? Any hints?
> --
> PL
>
|||Sean McCown wrote:
> Try backing up and restoring MSDB and changing the appropriate fields.
> We do this with jobs every week to keep 2 servers in sync and this is what
> we use to bring the jobs up to date. I would imagine that it could be just
> as easy for SSIS packages, though I haven't tried it officially.
> UPDATE sysjobs
> SET originating_server = 'MyServer'
> So just run that on the new server once you have MSDB restored on there and
> you should be OK. And just check the SSIS tables to discover similar entries
> that may need to be changed.
Right. But how to restore the msdb database? When I try to do it from
SMS (right click on database -> tasks -> restore) I get failure message
"Exclusive access could not be obtained because the database is in
use.", which makes sense but does not resolve the problem. There is also
no option to go off-line or detach for that database.
Should I just replace the msdb datafiles (mdf/ldf) with the ones from
'old' server?
PL
|||OK, there are a couple things here...
first, to restore MSDB just startup SQL with -T3608 and -m. 3608 prevents
startup of all system DBs except master. -m is single-user mode. So you
should now be able to restore MSDB with no problem. If you're doing it from
the command line, then use -c.
Second, You can always just setup a linked server and copy the raw data over
without restoring.
Good luck.
"Piotr Lipski" wrote:
> Sean McCown wrote:
> Right. But how to restore the msdb database? When I try to do it from
> SMS (right click on database -> tasks -> restore) I get failure message
> "Exclusive access could not be obtained because the database is in
> use.", which makes sense but does not resolve the problem. There is also
> no option to go off-line or detach for that database.
> Should I just replace the msdb datafiles (mdf/ldf) with the ones from
> 'old' server?
> --
> PL
>
sqlsql
Is there any simple way of copying all of the ssis packages between two
servers?
I have just installed sql 2005 on a new, better equipped machine and I have
to move there all the data. Including ssis of course. There are about 40-50
packages to do (stored in the database, not in filesystem) and I hope there
is a better way than just to import packages (one by one) to a text file
and export them to another server.
BTW, I'm going to copy the job definitions as well, there are about 20 jobs
defined on the server, is there any handy way of doing this? Any hints?
PL
Try backing up and restoring MSDB and changing the appropriate fields.
We do this with jobs every week to keep 2 servers in sync and this is what
we use to bring the jobs up to date. I would imagine that it could be just
as easy for SSIS packages, though I haven't tried it officially.
UPDATE sysjobs
SET originating_server = 'MyServer'
So just run that on the new server once you have MSDB restored on there and
you should be OK. And just check the SSIS tables to discover similar entries
that may need to be changed.
"Piotr Lipski" wrote:
> Hi.
> Is there any simple way of copying all of the ssis packages between two
> servers?
> I have just installed sql 2005 on a new, better equipped machine and I have
> to move there all the data. Including ssis of course. There are about 40-50
> packages to do (stored in the database, not in filesystem) and I hope there
> is a better way than just to import packages (one by one) to a text file
> and export them to another server.
> BTW, I'm going to copy the job definitions as well, there are about 20 jobs
> defined on the server, is there any handy way of doing this? Any hints?
> --
> PL
>
|||Sean McCown wrote:
> Try backing up and restoring MSDB and changing the appropriate fields.
> We do this with jobs every week to keep 2 servers in sync and this is what
> we use to bring the jobs up to date. I would imagine that it could be just
> as easy for SSIS packages, though I haven't tried it officially.
> UPDATE sysjobs
> SET originating_server = 'MyServer'
> So just run that on the new server once you have MSDB restored on there and
> you should be OK. And just check the SSIS tables to discover similar entries
> that may need to be changed.
Right. But how to restore the msdb database? When I try to do it from
SMS (right click on database -> tasks -> restore) I get failure message
"Exclusive access could not be obtained because the database is in
use.", which makes sense but does not resolve the problem. There is also
no option to go off-line or detach for that database.
Should I just replace the msdb datafiles (mdf/ldf) with the ones from
'old' server?
PL
|||OK, there are a couple things here...
first, to restore MSDB just startup SQL with -T3608 and -m. 3608 prevents
startup of all system DBs except master. -m is single-user mode. So you
should now be able to restore MSDB with no problem. If you're doing it from
the command line, then use -c.
Second, You can always just setup a linked server and copy the raw data over
without restoring.
Good luck.
"Piotr Lipski" wrote:
> Sean McCown wrote:
> Right. But how to restore the msdb database? When I try to do it from
> SMS (right click on database -> tasks -> restore) I get failure message
> "Exclusive access could not be obtained because the database is in
> use.", which makes sense but does not resolve the problem. There is also
> no option to go off-line or detach for that database.
> Should I just replace the msdb datafiles (mdf/ldf) with the ones from
> 'old' server?
> --
> PL
>
sqlsql
Copy local sql 05 DB to production machine
Hi SQL folks,
I've googled for this the whole yesterday and I couldn't find a complete solution.
I'm having a sql2005 database in my development machine and I need to copy all the content "Tables, Diagrams, PK columns and other data" to the remote production machine.
Using the Import/Export method didn't copied the relationships between tables, also it turned the PKs into just a standard columns
Can anyone help?
The only missing thing now is the relationships, How can I copy it?
I've copied the DB diagram but the relationships simply disapeared!
sqlsqlTuesday, March 27, 2012
copy file automatically
I need to copy files from one machine to another machine. It should be done automatically. Could you please give me a suggestion. I have no idea about this. It should write a script or program. But I have no idea yet,
Thanksxcopy utility would help..|||Can you give me more detail about xcopy utility? Where is it? how can i learn it? Thanks in advance.|||open a dos window.
at the prompt type: help xcopy|||i try this in cmd command:
C:\>xcopy c:YTEST \\Server25702\C:\YTEST1
i want to copy the YTEST file to another machine (called Server25702). but it gave me a error message:
Invalid drive specification
0 File(s) copied
What wrong with it, also i change Server25702 to IP address, it also gave me a same message. Can you help me again? Thanks.|||You have to map a drive to \\server25702\c:\ytest1 before you can use xcopy.
So if you use the map command to map drive letter D - your syntax would be:
xcopy c:\ytest d:\ytest
i try this in cmd command:
C:\>xcopy c:YTEST \\Server25702\C:\YTEST1
i want to copy the YTEST file to another machine (called Server25702). but it gave me a error message:
Invalid drive specification
0 File(s) copied
What wrong with it, also i change Server25702 to IP address, it also gave me a same message. Can you help me again? Thanks.|||i try to use map drive, i type \\Server25702, it give me message, the network drive can't be found. Why? Thanks.|||you will need to share the drive on server25702|||Thanks, i got it.
But after i copied, i found all the folder in the source file didn't copy to destination, Can this copy anything in the folder i selected to the destination?
I am going to save it as .bat file, How can i use window to schedule it to run from Monday to Friday. Thanks.
Thanksxcopy utility would help..|||Can you give me more detail about xcopy utility? Where is it? how can i learn it? Thanks in advance.|||open a dos window.
at the prompt type: help xcopy|||i try this in cmd command:
C:\>xcopy c:YTEST \\Server25702\C:\YTEST1
i want to copy the YTEST file to another machine (called Server25702). but it gave me a error message:
Invalid drive specification
0 File(s) copied
What wrong with it, also i change Server25702 to IP address, it also gave me a same message. Can you help me again? Thanks.|||You have to map a drive to \\server25702\c:\ytest1 before you can use xcopy.
So if you use the map command to map drive letter D - your syntax would be:
xcopy c:\ytest d:\ytest
i try this in cmd command:
C:\>xcopy c:YTEST \\Server25702\C:\YTEST1
i want to copy the YTEST file to another machine (called Server25702). but it gave me a error message:
Invalid drive specification
0 File(s) copied
What wrong with it, also i change Server25702 to IP address, it also gave me a same message. Can you help me again? Thanks.|||i try to use map drive, i type \\Server25702, it give me message, the network drive can't be found. Why? Thanks.|||you will need to share the drive on server25702|||Thanks, i got it.
But after i copied, i found all the folder in the source file didn't copy to destination, Can this copy anything in the folder i selected to the destination?
I am going to save it as .bat file, How can i use window to schedule it to run from Monday to Friday. Thanks.
Sunday, March 25, 2012
Copy DB to a different Machine
Hi,
I have developed an application using SQl Server 2000.
I want to transfer the database to my new server. I want all the tables and datas to be transferred.
I am new to this application. So i am not able to get mysel started. Can someone help me in this problem.
My database is large. It has stored procedures, database diagrams.
Any help in this regard would be highly appreciated.
Thanks,
-sriramFin MS Sql Server on your Programs menu. Choose 'Import/Export' data > next. The following Dialogue is the From dialogue. Choose the Databse you want to copy and press next. In the 'To' dialogue, enter the IP/URL to the remote SQL Server. In the Dropdown list, choose '<New>' and name your Database - press OK. I nteh next dialogue, choose 'Copy objects and data between SQL Server databases'. Click Next 3 times and then End. Now your Database and data will be copied to your new Server.|||I prefer doing a full backup and then restoring the backup on the new machine. I find it quicker that way. This way your DB Diagrams will survive too.|||i agree with the full backup technique.
the only time i "object copy" between db's is to keep my local DB in sync with a shared Development DB and 2 other developers.|||Hi,
Thanks for replying.
How can i do a full backup. I am not able to backup and transfer to the new machine.
So can you help me??
thanks,
-sriram|||if you go to C:\Program Files\Microsoft SQL Server\MSSQL\Data
find your db files ...( 2- the db file and the log file)
copy them over to the new machine in the same data folder...and "attach" the db...
** remember to "Stop" the sql server before you do this...
hth|||I'm working on a project with 3 other people whom are using MSDE for the DB. Is there a function similar to 'attach db' that can be used with MSDE. Our computers are not networked, so we will only be able to pass the database file around.
Thanks in advance!
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
Thursday, March 22, 2012
Copy Database, can't attach it?
I'm used the Copy Database Wizard to copy a database from one server to
another. While in the copy operation the destination machine was hanging and
I had to reset it.
Now when I want to attach the source database again, I get the following
error:
"CREATE FILE encountered operating system error 5 (Access is denied.)..."
What is going on here? Why was the source machine affected in this
destructive manner?
What do I need to do in order to attach my source again?
OlavI generally find that it's 10x easier to shoot yourself in the foot and get
into serious trouble with SQL Server 2005 than it was with SQL Server 2000.
Olav
"Olav" <x@.y.com> wrote in message
news:O0Fj8YZXGHA.4212@.TK2MSFTNGP02.phx.gbl...
> I'm used the Copy Database Wizard to copy a database from one server to
> another. While in the copy operation the destination machine was hanging
> and I had to reset it.
> Now when I want to attach the source database again, I get the following
> error:
> "CREATE FILE encountered operating system error 5 (Access is denied.)..."
> What is going on here? Why was the source machine affected in this
> destructive manner?
> What do I need to do in order to attach my source again?
> Olav
>|||I read somewhere detaching databases is very risky, and can infact
corrupt the entire database if something goes wrong... Good luck to
you.|||?
Nice if that is the default option the Copy Database Wizard is using then?
Olav
"KBuser" <Kyle.Buser@.gmail.com> wrote in message
news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
>I read somewhere detaching databases is very risky, and can infact
> corrupt the entire database if something goes wrong... Good luck to
> you.
>|||Stop me if im boring you ...
Basically a database created using created database Test consists of 2 files
mdf for tables
ldf for transaction logs
In effect detaching a database is what happens when you stop sql server
attaching is what happens when you start sql server
so dont be afraid of this process
Be aware though that ...
Any transactions not written down to the mdf file and still in the ldf
transaction logs will need to be recovered by SQL server.
to limit this complication we
stop all users
run checkpoint 3 times to for those transactions down into mdf
then detach
at this point the logfile is emptied and can be ditched on attach
Ever wanted to shink you log file. then this method can be employed.
Note I would not used this method on prodction systems crital to business..
Lifes too short and its a hassel geting another job.
If you detached thdatabase then you basicall have 2 files
If a file gets chopped on a copy you would normally tidy up and resend file.
hope this helps
"Olav" wrote:
> ?
> Nice if that is the default option the Copy Database Wizard is using then?
> Olav
> "KBuser" <Kyle.Buser@.gmail.com> wrote in message
> news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
>
>|||"KBuser" <Kyle.Buser@.gmail.com> wrote in message
news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
> I read somewhere detaching databases is very risky, and can infact
> corrupt the entire database if something goes wrong... Good luck to
> you.
No, detaching a database should be perfectly fine.
But you need to copy both the MDF and LDF files and attach both.
>
another. While in the copy operation the destination machine was hanging and
I had to reset it.
Now when I want to attach the source database again, I get the following
error:
"CREATE FILE encountered operating system error 5 (Access is denied.)..."
What is going on here? Why was the source machine affected in this
destructive manner?
What do I need to do in order to attach my source again?
OlavI generally find that it's 10x easier to shoot yourself in the foot and get
into serious trouble with SQL Server 2005 than it was with SQL Server 2000.
Olav
"Olav" <x@.y.com> wrote in message
news:O0Fj8YZXGHA.4212@.TK2MSFTNGP02.phx.gbl...
> I'm used the Copy Database Wizard to copy a database from one server to
> another. While in the copy operation the destination machine was hanging
> and I had to reset it.
> Now when I want to attach the source database again, I get the following
> error:
> "CREATE FILE encountered operating system error 5 (Access is denied.)..."
> What is going on here? Why was the source machine affected in this
> destructive manner?
> What do I need to do in order to attach my source again?
> Olav
>|||I read somewhere detaching databases is very risky, and can infact
corrupt the entire database if something goes wrong... Good luck to
you.|||?
Nice if that is the default option the Copy Database Wizard is using then?
Olav
"KBuser" <Kyle.Buser@.gmail.com> wrote in message
news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
>I read somewhere detaching databases is very risky, and can infact
> corrupt the entire database if something goes wrong... Good luck to
> you.
>|||Stop me if im boring you ...
Basically a database created using created database Test consists of 2 files
mdf for tables
ldf for transaction logs
In effect detaching a database is what happens when you stop sql server
attaching is what happens when you start sql server
so dont be afraid of this process
Be aware though that ...
Any transactions not written down to the mdf file and still in the ldf
transaction logs will need to be recovered by SQL server.
to limit this complication we
stop all users
run checkpoint 3 times to for those transactions down into mdf
then detach
at this point the logfile is emptied and can be ditched on attach
Ever wanted to shink you log file. then this method can be employed.
Note I would not used this method on prodction systems crital to business..
Lifes too short and its a hassel geting another job.
If you detached thdatabase then you basicall have 2 files
If a file gets chopped on a copy you would normally tidy up and resend file.
hope this helps
"Olav" wrote:
> ?
> Nice if that is the default option the Copy Database Wizard is using then?
> Olav
> "KBuser" <Kyle.Buser@.gmail.com> wrote in message
> news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
>
>|||"KBuser" <Kyle.Buser@.gmail.com> wrote in message
news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
> I read somewhere detaching databases is very risky, and can infact
> corrupt the entire database if something goes wrong... Good luck to
> you.
No, detaching a database should be perfectly fine.
But you need to copy both the MDF and LDF files and attach both.
>
Copy Database, can't attach it?
I'm used the Copy Database Wizard to copy a database from one server to
another. While in the copy operation the destination machine was hanging and
I had to reset it.
Now when I want to attach the source database again, I get the following
error:
"CREATE FILE encountered operating system error 5 (Access is denied.)..."
What is going on here? Why was the source machine affected in this
destructive manner?
What do I need to do in order to attach my source again?
OlavI generally find that it's 10x easier to shoot yourself in the foot and get
into serious trouble with SQL Server 2005 than it was with SQL Server 2000.
Olav
"Olav" <x@.y.com> wrote in message
news:O0Fj8YZXGHA.4212@.TK2MSFTNGP02.phx.gbl...
> I'm used the Copy Database Wizard to copy a database from one server to
> another. While in the copy operation the destination machine was hanging
> and I had to reset it.
> Now when I want to attach the source database again, I get the following
> error:
> "CREATE FILE encountered operating system error 5 (Access is denied.)..."
> What is going on here? Why was the source machine affected in this
> destructive manner?
> What do I need to do in order to attach my source again?
> Olav
>|||I read somewhere detaching databases is very risky, and can infact
corrupt the entire database if something goes wrong... Good luck to
you.|||?
Nice if that is the default option the Copy Database Wizard is using then?
Olav
"KBuser" <Kyle.Buser@.gmail.com> wrote in message
news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
>I read somewhere detaching databases is very risky, and can infact
> corrupt the entire database if something goes wrong... Good luck to
> you.
>|||Stop me if im boring you ...
Basically a database created using created database Test consists of 2 files
mdf for tables
ldf for transaction logs
In effect detaching a database is what happens when you stop sql server
attaching is what happens when you start sql server
so dont be afraid of this process
Be aware though that ...
Any transactions not written down to the mdf file and still in the ldf
transaction logs will need to be recovered by SQL server.
to limit this complication we
stop all users
run checkpoint 3 times to for those transactions down into mdf
then detach
at this point the logfile is emptied and can be ditched on attach
Ever wanted to shink you log file. then this method can be employed.
Note I would not used this method on prodction systems crital to business..
Lifes too short and its a hassel geting another job.
If you detached thdatabase then you basicall have 2 files
If a file gets chopped on a copy you would normally tidy up and resend file.
hope this helps
"Olav" wrote:
> ?
> Nice if that is the default option the Copy Database Wizard is using then?
> Olav
> "KBuser" <Kyle.Buser@.gmail.com> wrote in message
> news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
> >I read somewhere detaching databases is very risky, and can infact
> > corrupt the entire database if something goes wrong... Good luck to
> > you.
> >
>
>|||"KBuser" <Kyle.Buser@.gmail.com> wrote in message
news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
> I read somewhere detaching databases is very risky, and can infact
> corrupt the entire database if something goes wrong... Good luck to
> you.
No, detaching a database should be perfectly fine.
But you need to copy both the MDF and LDF files and attach both.
>
another. While in the copy operation the destination machine was hanging and
I had to reset it.
Now when I want to attach the source database again, I get the following
error:
"CREATE FILE encountered operating system error 5 (Access is denied.)..."
What is going on here? Why was the source machine affected in this
destructive manner?
What do I need to do in order to attach my source again?
OlavI generally find that it's 10x easier to shoot yourself in the foot and get
into serious trouble with SQL Server 2005 than it was with SQL Server 2000.
Olav
"Olav" <x@.y.com> wrote in message
news:O0Fj8YZXGHA.4212@.TK2MSFTNGP02.phx.gbl...
> I'm used the Copy Database Wizard to copy a database from one server to
> another. While in the copy operation the destination machine was hanging
> and I had to reset it.
> Now when I want to attach the source database again, I get the following
> error:
> "CREATE FILE encountered operating system error 5 (Access is denied.)..."
> What is going on here? Why was the source machine affected in this
> destructive manner?
> What do I need to do in order to attach my source again?
> Olav
>|||I read somewhere detaching databases is very risky, and can infact
corrupt the entire database if something goes wrong... Good luck to
you.|||?
Nice if that is the default option the Copy Database Wizard is using then?
Olav
"KBuser" <Kyle.Buser@.gmail.com> wrote in message
news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
>I read somewhere detaching databases is very risky, and can infact
> corrupt the entire database if something goes wrong... Good luck to
> you.
>|||Stop me if im boring you ...
Basically a database created using created database Test consists of 2 files
mdf for tables
ldf for transaction logs
In effect detaching a database is what happens when you stop sql server
attaching is what happens when you start sql server
so dont be afraid of this process
Be aware though that ...
Any transactions not written down to the mdf file and still in the ldf
transaction logs will need to be recovered by SQL server.
to limit this complication we
stop all users
run checkpoint 3 times to for those transactions down into mdf
then detach
at this point the logfile is emptied and can be ditched on attach
Ever wanted to shink you log file. then this method can be employed.
Note I would not used this method on prodction systems crital to business..
Lifes too short and its a hassel geting another job.
If you detached thdatabase then you basicall have 2 files
If a file gets chopped on a copy you would normally tidy up and resend file.
hope this helps
"Olav" wrote:
> ?
> Nice if that is the default option the Copy Database Wizard is using then?
> Olav
> "KBuser" <Kyle.Buser@.gmail.com> wrote in message
> news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
> >I read somewhere detaching databases is very risky, and can infact
> > corrupt the entire database if something goes wrong... Good luck to
> > you.
> >
>
>|||"KBuser" <Kyle.Buser@.gmail.com> wrote in message
news:1144783193.978615.83980@.t31g2000cwb.googlegroups.com...
> I read somewhere detaching databases is very risky, and can infact
> corrupt the entire database if something goes wrong... Good luck to
> you.
No, detaching a database should be perfectly fine.
But you need to copy both the MDF and LDF files and attach both.
>
Copy Database Wizard Problems
Hi,
I am trying to use the copy database wizard to copy a database from SQL
server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
on the create package step with error message "Error loading type
library/DLL". The first two steps (Add log for package and add tasks for
transfering database objects) are sucessful. What does this error message
means? How can I correct it?
Thanks,
JimHello Jim,
I would like to know more detailed information about your environment so
that I can provide more troubleshoot steps.
1. What's your OS version and SQL Server version?
2. Have you applied latest Service pack for the Sql server and Windows OS?
3. Are you using the 64bit OS?
I would also like for you to check if the following registry key is present
or
not. If so please export it and send it to me:
HKCR\Wow6432Node\ " "
In here search for a key with TypeLib GUID =
{D1D9A51E-B4FE-420B-97B1-28A383EF9168} >
If the key is present proceed to try registering the dlls below as
follows.
PLEASE PERFORM IN THE ORDER SPECIFIED:
Regsvr32 /u "C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\DTS.dll"
Regsvr32 /u "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
Regsvr32 "C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\DTS.dll"
Regsvr32 "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Jim
I assume this is from SQL 2000 to SQL 2005, have you tried running this from
SQL 2005 instead. Will the same thing happen if you save this as a package
and then run the package?
John
"Jim Zhao" wrote:
> Hi,
> I am trying to use the copy database wizard to copy a database from SQL
> server 2000 to SQL Server 2005 on the same machine. When I run it, it fail
s
> on the create package step with error message "Error loading type
> library/DLL". The first two steps (Add log for package and add tasks for
> transfering database objects) are sucessful. What does this error message
> means? How can I correct it?
> Thanks,
> Jim|||Hi
If using SQL 2005 this may help! http://support.microsoft.com/kb/918222/
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi Jim
> I assume this is from SQL 2000 to SQL 2005, have you tried running this fr
om
> SQL 2005 instead. Will the same thing happen if you save this as a package
> and then run the package?
> John
> "Jim Zhao" wrote:
>|||Jim Zhao wrote:
> Hi,
> I am trying to use the copy database wizard to copy a database from SQL
> server 2000 to SQL Server 2005 on the same machine. When I run it, it fail
s
> on the create package step with error message "Error loading type
> library/DLL". The first two steps (Add log for package and add tasks for
> transfering database objects) are sucessful. What does this error message
> means? How can I correct it?
> Thanks,
> Jim
You might consider doing yourself a favor by doing a backup/restore to
"copy" your database, instead of using this wizard... Easier, faster,
and you can TROUBLESHOOT it if it doesn't work...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
I am trying to use the copy database wizard to copy a database from SQL
server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
on the create package step with error message "Error loading type
library/DLL". The first two steps (Add log for package and add tasks for
transfering database objects) are sucessful. What does this error message
means? How can I correct it?
Thanks,
JimHello Jim,
I would like to know more detailed information about your environment so
that I can provide more troubleshoot steps.
1. What's your OS version and SQL Server version?
2. Have you applied latest Service pack for the Sql server and Windows OS?
3. Are you using the 64bit OS?
I would also like for you to check if the following registry key is present
or
not. If so please export it and send it to me:
HKCR\Wow6432Node\ " "
In here search for a key with TypeLib GUID =
{D1D9A51E-B4FE-420B-97B1-28A383EF9168} >
If the key is present proceed to try registering the dlls below as
follows.
PLEASE PERFORM IN THE ORDER SPECIFIED:
Regsvr32 /u "C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\DTS.dll"
Regsvr32 /u "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
Regsvr32 "C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\DTS.dll"
Regsvr32 "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Jim
I assume this is from SQL 2000 to SQL 2005, have you tried running this from
SQL 2005 instead. Will the same thing happen if you save this as a package
and then run the package?
John
"Jim Zhao" wrote:
> Hi,
> I am trying to use the copy database wizard to copy a database from SQL
> server 2000 to SQL Server 2005 on the same machine. When I run it, it fail
s
> on the create package step with error message "Error loading type
> library/DLL". The first two steps (Add log for package and add tasks for
> transfering database objects) are sucessful. What does this error message
> means? How can I correct it?
> Thanks,
> Jim|||Hi
If using SQL 2005 this may help! http://support.microsoft.com/kb/918222/
John
"John Bell" wrote:
[vbcol=seagreen]
> Hi Jim
> I assume this is from SQL 2000 to SQL 2005, have you tried running this fr
om
> SQL 2005 instead. Will the same thing happen if you save this as a package
> and then run the package?
> John
> "Jim Zhao" wrote:
>|||Jim Zhao wrote:
> Hi,
> I am trying to use the copy database wizard to copy a database from SQL
> server 2000 to SQL Server 2005 on the same machine. When I run it, it fail
s
> on the create package step with error message "Error loading type
> library/DLL". The first two steps (Add log for package and add tasks for
> transfering database objects) are sucessful. What does this error message
> means? How can I correct it?
> Thanks,
> Jim
You might consider doing yourself a favor by doing a backup/restore to
"copy" your database, instead of using this wizard... Easier, faster,
and you can TROUBLESHOOT it if it doesn't work...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Copy Database Wizard Problems
Hi,
I am trying to use the copy database wizard to copy a database from SQL
server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
on the create package step with error message "Error loading type
library/DLL". The first two steps (Add log for package and add tasks for
transfering database objects) are sucessful. What does this error message
means? How can I correct it?
Thanks,
JimHello Jim,
I would like to know more detailed information about your environment so
that I can provide more troubleshoot steps.
1. What's your OS version and SQL Server version?
2. Have you applied latest Service pack for the Sql server and Windows OS?
3. Are you using the 64bit OS?
I would also like for you to check if the following registry key is present
or
not. If so please export it and send it to me:
HKCR\Wow6432Node\ " "
In here search for a key with TypeLib GUID ={D1D9A51E-B4FE-420B-97B1-28A383EF9168} >
If the key is present proceed to try registering the dlls below as
follows.
PLEASE PERFORM IN THE ORDER SPECIFIED:
Regsvr32 /u "C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\DTS.dll"
Regsvr32 /u "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
Regsvr32 "C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\DTS.dll"
Regsvr32 "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Jim
I assume this is from SQL 2000 to SQL 2005, have you tried running this from
SQL 2005 instead. Will the same thing happen if you save this as a package
and then run the package?
John
"Jim Zhao" wrote:
> Hi,
> I am trying to use the copy database wizard to copy a database from SQL
> server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
> on the create package step with error message "Error loading type
> library/DLL". The first two steps (Add log for package and add tasks for
> transfering database objects) are sucessful. What does this error message
> means? How can I correct it?
> Thanks,
> Jim|||Hi
If using SQL 2005 this may help! http://support.microsoft.com/kb/918222/
John
"John Bell" wrote:
> Hi Jim
> I assume this is from SQL 2000 to SQL 2005, have you tried running this from
> SQL 2005 instead. Will the same thing happen if you save this as a package
> and then run the package?
> John
> "Jim Zhao" wrote:
> > Hi,
> >
> > I am trying to use the copy database wizard to copy a database from SQL
> > server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
> > on the create package step with error message "Error loading type
> > library/DLL". The first two steps (Add log for package and add tasks for
> > transfering database objects) are sucessful. What does this error message
> > means? How can I correct it?
> >
> > Thanks,
> > Jim|||Jim Zhao wrote:
> Hi,
> I am trying to use the copy database wizard to copy a database from SQL
> server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
> on the create package step with error message "Error loading type
> library/DLL". The first two steps (Add log for package and add tasks for
> transfering database objects) are sucessful. What does this error message
> means? How can I correct it?
> Thanks,
> Jim
You might consider doing yourself a favor by doing a backup/restore to
"copy" your database, instead of using this wizard... Easier, faster,
and you can TROUBLESHOOT it if it doesn't work...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.sqlsql
I am trying to use the copy database wizard to copy a database from SQL
server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
on the create package step with error message "Error loading type
library/DLL". The first two steps (Add log for package and add tasks for
transfering database objects) are sucessful. What does this error message
means? How can I correct it?
Thanks,
JimHello Jim,
I would like to know more detailed information about your environment so
that I can provide more troubleshoot steps.
1. What's your OS version and SQL Server version?
2. Have you applied latest Service pack for the Sql server and Windows OS?
3. Are you using the 64bit OS?
I would also like for you to check if the following registry key is present
or
not. If so please export it and send it to me:
HKCR\Wow6432Node\ " "
In here search for a key with TypeLib GUID ={D1D9A51E-B4FE-420B-97B1-28A383EF9168} >
If the key is present proceed to try registering the dlls below as
follows.
PLEASE PERFORM IN THE ORDER SPECIFIED:
Regsvr32 /u "C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\DTS.dll"
Regsvr32 /u "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
Regsvr32 "C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\DTS.dll"
Regsvr32 "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi Jim
I assume this is from SQL 2000 to SQL 2005, have you tried running this from
SQL 2005 instead. Will the same thing happen if you save this as a package
and then run the package?
John
"Jim Zhao" wrote:
> Hi,
> I am trying to use the copy database wizard to copy a database from SQL
> server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
> on the create package step with error message "Error loading type
> library/DLL". The first two steps (Add log for package and add tasks for
> transfering database objects) are sucessful. What does this error message
> means? How can I correct it?
> Thanks,
> Jim|||Hi
If using SQL 2005 this may help! http://support.microsoft.com/kb/918222/
John
"John Bell" wrote:
> Hi Jim
> I assume this is from SQL 2000 to SQL 2005, have you tried running this from
> SQL 2005 instead. Will the same thing happen if you save this as a package
> and then run the package?
> John
> "Jim Zhao" wrote:
> > Hi,
> >
> > I am trying to use the copy database wizard to copy a database from SQL
> > server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
> > on the create package step with error message "Error loading type
> > library/DLL". The first two steps (Add log for package and add tasks for
> > transfering database objects) are sucessful. What does this error message
> > means? How can I correct it?
> >
> > Thanks,
> > Jim|||Jim Zhao wrote:
> Hi,
> I am trying to use the copy database wizard to copy a database from SQL
> server 2000 to SQL Server 2005 on the same machine. When I run it, it fails
> on the create package step with error message "Error loading type
> library/DLL". The first two steps (Add log for package and add tasks for
> transfering database objects) are sucessful. What does this error message
> means? How can I correct it?
> Thanks,
> Jim
You might consider doing yourself a favor by doing a backup/restore to
"copy" your database, instead of using this wizard... Easier, faster,
and you can TROUBLESHOOT it if it doesn't work...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.sqlsql
Copy Database Wizard on Vista x64 machine
I've got a new Vista x64 build with SQL2005 (+SP2) freshly installed. I'm
now trying to copy existing databased from other services but I can't get it
to work. I get the following error logged in the Event Viewer Application
Log:
"Log Name: Application
Source: Application Error
Date: 29/11/2007 16:16:56
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: mycomputer
Description:
The description for Event ID 1000 from source Application Error cannot be
found. Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
The following information was included with the event:
DTExec.exe
2005.90.3042.0
45cd7539
kernel32.dll
6.0.6000.16386
4549d328
e053534f
00000000000233ac
The substitution string for insert index (%1) could not be found"
I cant find anything online that enlightens me - I know that Vista needs SP
installed to work, so I've installed it:
@.@.Version=
Microsoft SQL Server 2005 - 9.00.3054.00 (X64)
Mar 23 2007 18:41:50
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.0 (Build 6000: )
All the services are running under a domain user that has access to the
areas where the data is stored, both source and destination, so I'm hoping
it's not a permissions issue - if it is, I wouldnt know where to look.
I *could* copy a local database to the same server (renamed of course), so
it suggests that the server is largely OK - does this suggest it *is* a
permissions issue?
The domain user that the services are running under are not in the local
Administrators group, but they are in the
SQLServer2005MSSQLUser$MyComputer$MSSQLS
ERVER group - which I assume is the
group that was set up by the SQL Server Provisioning Tool for Vista.
This is a development machine so I frequently want to copy different
versions of different databases backwards and forwards.
Any suggestions? Any other Vista x64-ers out there?
Thanks in advance...
ChrisSQL Server uses Active Directory accounts and groups for its
permissions.
Active Directory accounts and groups are represented by GUIDs that are
unique to a particular Active Directory Domain which is run by a
Primary Domain Contoroller. If your new Vista machine is not part of
a network, or is on a different domain than the old one, then it
probably uses different GUIDs for the active directory accounts than
the source machine did. If you copied over the SQL Server database
using a backup, then you probably also copied all the old GUIDs for
the SQL Server accounts that point to the GUIDs on the old machine,
and not the ones on new machine.
This means that your SQL Server accounts are out of sync with active
directory. you may have to recreate your SQL Server accounts on the
new machine.
Permissions are assigned through SQL Server Management Studio in two
steps. First, you assign the active directory accounts that are
allowed to connect to a SQL Server instance. This is done by right
clicking the Logins folder under the Security folder of the SQL Server
instance the user is to connect to and selecting New Login.
Then, you assign what SQL Server instance users are allowed to connect
to a particular database within an instance. This is done by right
clicking the Security folder under the database you want to give
permission for and selecting New->user.
In both cases, an extensive permissions dialog will open. For the
Login folder, you only have to specify an active directory account.
For the Security folder, you have to click securables in the left
sidebar, add the entities you want to view (tables), and then set
select, reference, update, delete, and insert permissions. There are
more steps, but this should point you in the right direction.|||Andy, thanks for your reply...
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:1ee305c9-338f-4a4f-9a42-198b42c597b5@.w40g2000hsb.googlegroups.com...
> If your new Vista machine is not part of
> a network, or is on a different domain than the old one,
>
My new machine is part of the same Domain and is recognised within Active
Directory.
> Permissions are assigned through SQL Server Management Studio in two
> steps. First, you assign the active directory accounts that are
> allowed to connect to a SQL Server instance. This is done by right
> clicking the Logins folder under the Security folder of the SQL Server
> instance the user is to connect to and selecting New Login.
Each human administrator is per of an SQL Admins group as are each of the
domain users that the different servers run under. On each server, the SQL
Admins group is added with a login and has sufficiend permissions (AFAIK).
> Then, you assign what SQL Server instance users are allowed to connect
> to a particular database within an instance. This is done by right
> clicking the Security folder under the database you want to give
> permission for and selecting New->user.
>
Done
> In both cases, an extensive permissions dialog will open. For the
> Login folder, you only have to specify an active directory account.
> For the Security folder, you have to click securables in the left
> sidebar, add the entities you want to view (tables), and then set
> select, reference, update, delete, and insert permissions. There are
> more steps, but this should point you in the right direction.
>
The login is set as a sysdamin so surely this shouldnt be necessary?
Somewhere in my tweaking, I've changed something. I *think* it's for the
better - I'm still getting errors but I'm getting further along.
I'm now getting Error 12550: Access to the path
'\\MyServer\MyShare\MyDB.mdf' is denied. The SQL Admins group has read/write
permissions to this area so I'm puzzled.
This is immediately followed by another Error 12550: Object reference not
set to an instance of an object. There are other errors further on, but I
think they are just as a consequence of these earlier errors.
I'm actually going to start copying backups because I need to crack on with
things, but I'm determined to get to the bottom of this. In my work, this
wizard is very useful so I'd rather not have to work around it.
Any further ideas?
Cheers
Chris
now trying to copy existing databased from other services but I can't get it
to work. I get the following error logged in the Event Viewer Application
Log:
"Log Name: Application
Source: Application Error
Date: 29/11/2007 16:16:56
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: mycomputer
Description:
The description for Event ID 1000 from source Application Error cannot be
found. Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
The following information was included with the event:
DTExec.exe
2005.90.3042.0
45cd7539
kernel32.dll
6.0.6000.16386
4549d328
e053534f
00000000000233ac
The substitution string for insert index (%1) could not be found"
I cant find anything online that enlightens me - I know that Vista needs SP
installed to work, so I've installed it:
@.@.Version=
Microsoft SQL Server 2005 - 9.00.3054.00 (X64)
Mar 23 2007 18:41:50
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.0 (Build 6000: )
All the services are running under a domain user that has access to the
areas where the data is stored, both source and destination, so I'm hoping
it's not a permissions issue - if it is, I wouldnt know where to look.
I *could* copy a local database to the same server (renamed of course), so
it suggests that the server is largely OK - does this suggest it *is* a
permissions issue?
The domain user that the services are running under are not in the local
Administrators group, but they are in the
SQLServer2005MSSQLUser$MyComputer$MSSQLS
ERVER group - which I assume is the
group that was set up by the SQL Server Provisioning Tool for Vista.
This is a development machine so I frequently want to copy different
versions of different databases backwards and forwards.
Any suggestions? Any other Vista x64-ers out there?
Thanks in advance...
ChrisSQL Server uses Active Directory accounts and groups for its
permissions.
Active Directory accounts and groups are represented by GUIDs that are
unique to a particular Active Directory Domain which is run by a
Primary Domain Contoroller. If your new Vista machine is not part of
a network, or is on a different domain than the old one, then it
probably uses different GUIDs for the active directory accounts than
the source machine did. If you copied over the SQL Server database
using a backup, then you probably also copied all the old GUIDs for
the SQL Server accounts that point to the GUIDs on the old machine,
and not the ones on new machine.
This means that your SQL Server accounts are out of sync with active
directory. you may have to recreate your SQL Server accounts on the
new machine.
Permissions are assigned through SQL Server Management Studio in two
steps. First, you assign the active directory accounts that are
allowed to connect to a SQL Server instance. This is done by right
clicking the Logins folder under the Security folder of the SQL Server
instance the user is to connect to and selecting New Login.
Then, you assign what SQL Server instance users are allowed to connect
to a particular database within an instance. This is done by right
clicking the Security folder under the database you want to give
permission for and selecting New->user.
In both cases, an extensive permissions dialog will open. For the
Login folder, you only have to specify an active directory account.
For the Security folder, you have to click securables in the left
sidebar, add the entities you want to view (tables), and then set
select, reference, update, delete, and insert permissions. There are
more steps, but this should point you in the right direction.|||Andy, thanks for your reply...
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:1ee305c9-338f-4a4f-9a42-198b42c597b5@.w40g2000hsb.googlegroups.com...
> If your new Vista machine is not part of
> a network, or is on a different domain than the old one,
>
My new machine is part of the same Domain and is recognised within Active
Directory.
> Permissions are assigned through SQL Server Management Studio in two
> steps. First, you assign the active directory accounts that are
> allowed to connect to a SQL Server instance. This is done by right
> clicking the Logins folder under the Security folder of the SQL Server
> instance the user is to connect to and selecting New Login.
Each human administrator is per of an SQL Admins group as are each of the
domain users that the different servers run under. On each server, the SQL
Admins group is added with a login and has sufficiend permissions (AFAIK).
> Then, you assign what SQL Server instance users are allowed to connect
> to a particular database within an instance. This is done by right
> clicking the Security folder under the database you want to give
> permission for and selecting New->user.
>
Done
> In both cases, an extensive permissions dialog will open. For the
> Login folder, you only have to specify an active directory account.
> For the Security folder, you have to click securables in the left
> sidebar, add the entities you want to view (tables), and then set
> select, reference, update, delete, and insert permissions. There are
> more steps, but this should point you in the right direction.
>
The login is set as a sysdamin so surely this shouldnt be necessary?
Somewhere in my tweaking, I've changed something. I *think* it's for the
better - I'm still getting errors but I'm getting further along.
I'm now getting Error 12550: Access to the path
'\\MyServer\MyShare\MyDB.mdf' is denied. The SQL Admins group has read/write
permissions to this area so I'm puzzled.
This is immediately followed by another Error 12550: Object reference not
set to an instance of an object. There are other errors further on, but I
think they are just as a consequence of these earlier errors.
I'm actually going to start copying backups because I need to crack on with
things, but I'm determined to get to the bottom of this. In my work, this
wizard is very useful so I'd rather not have to work around it.
Any further ideas?
Cheers
Chris
Copy Database Wizard on Vista x64 machine
I've got a new Vista x64 build with SQL2005 (+SP2) freshly installed. I'm
now trying to copy existing databased from other services but I can't get it
to work. I get the following error logged in the Event Viewer Application
Log:
"Log Name: Application
Source: Application Error
Date: 29/11/2007 16:16:56
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: mycomputer
Description:
The description for Event ID 1000 from source Application Error cannot be
found. Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
The following information was included with the event:
DTExec.exe
2005.90.3042.0
45cd7539
kernel32.dll
6.0.6000.16386
4549d328
e053534f
00000000000233ac
The substitution string for insert index (%1) could not be found"
I cant find anything online that enlightens me - I know that Vista needs SP
installed to work, so I've installed it:
@.@.Version= Microsoft SQL Server 2005 - 9.00.3054.00 (X64)
Mar 23 2007 18:41:50
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.0 (Build 6000: )
All the services are running under a domain user that has access to the
areas where the data is stored, both source and destination, so I'm hoping
it's not a permissions issue - if it is, I wouldnt know where to look.
I *could* copy a local database to the same server (renamed of course), so
it suggests that the server is largely OK - does this suggest it *is* a
permissions issue?
The domain user that the services are running under are not in the local
Administrators group, but they are in the
SQLServer2005MSSQLUser$MyComputer$MSSQLSERVER group - which I assume is the
group that was set up by the SQL Server Provisioning Tool for Vista.
This is a development machine so I frequently want to copy different
versions of different databases backwards and forwards.
Any suggestions? Any other Vista x64-ers out there?
Thanks in advance...
ChrisSQL Server uses Active Directory accounts and groups for its
permissions.
Active Directory accounts and groups are represented by GUIDs that are
unique to a particular Active Directory Domain which is run by a
Primary Domain Contoroller. If your new Vista machine is not part of
a network, or is on a different domain than the old one, then it
probably uses different GUIDs for the active directory accounts than
the source machine did. If you copied over the SQL Server database
using a backup, then you probably also copied all the old GUIDs for
the SQL Server accounts that point to the GUIDs on the old machine,
and not the ones on new machine.
This means that your SQL Server accounts are out of sync with active
directory. you may have to recreate your SQL Server accounts on the
new machine.
Permissions are assigned through SQL Server Management Studio in two
steps. First, you assign the active directory accounts that are
allowed to connect to a SQL Server instance. This is done by right
clicking the Logins folder under the Security folder of the SQL Server
instance the user is to connect to and selecting New Login.
Then, you assign what SQL Server instance users are allowed to connect
to a particular database within an instance. This is done by right
clicking the Security folder under the database you want to give
permission for and selecting New->user.
In both cases, an extensive permissions dialog will open. For the
Login folder, you only have to specify an active directory account.
For the Security folder, you have to click securables in the left
sidebar, add the entities you want to view (tables), and then set
select, reference, update, delete, and insert permissions. There are
more steps, but this should point you in the right direction.|||Andy, thanks for your reply...
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:1ee305c9-338f-4a4f-9a42-198b42c597b5@.w40g2000hsb.googlegroups.com...
> If your new Vista machine is not part of
> a network, or is on a different domain than the old one,
>
My new machine is part of the same Domain and is recognised within Active
Directory.
> Permissions are assigned through SQL Server Management Studio in two
> steps. First, you assign the active directory accounts that are
> allowed to connect to a SQL Server instance. This is done by right
> clicking the Logins folder under the Security folder of the SQL Server
> instance the user is to connect to and selecting New Login.
Each human administrator is per of an SQL Admins group as are each of the
domain users that the different servers run under. On each server, the SQL
Admins group is added with a login and has sufficiend permissions (AFAIK).
> Then, you assign what SQL Server instance users are allowed to connect
> to a particular database within an instance. This is done by right
> clicking the Security folder under the database you want to give
> permission for and selecting New->user.
>
Done
> In both cases, an extensive permissions dialog will open. For the
> Login folder, you only have to specify an active directory account.
> For the Security folder, you have to click securables in the left
> sidebar, add the entities you want to view (tables), and then set
> select, reference, update, delete, and insert permissions. There are
> more steps, but this should point you in the right direction.
>
The login is set as a sysdamin so surely this shouldnt be necessary?
Somewhere in my tweaking, I've changed something. I *think* it's for the
better - I'm still getting errors but I'm getting further along.
I'm now getting Error 12550: Access to the path
'\\MyServer\MyShare\MyDB.mdf' is denied. The SQL Admins group has read/write
permissions to this area so I'm puzzled.
This is immediately followed by another Error 12550: Object reference not
set to an instance of an object. There are other errors further on, but I
think they are just as a consequence of these earlier errors.
I'm actually going to start copying backups because I need to crack on with
things, but I'm determined to get to the bottom of this. In my work, this
wizard is very useful so I'd rather not have to work around it.
Any further ideas?
Cheers
Chrissqlsql
now trying to copy existing databased from other services but I can't get it
to work. I get the following error logged in the Event Viewer Application
Log:
"Log Name: Application
Source: Application Error
Date: 29/11/2007 16:16:56
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: mycomputer
Description:
The description for Event ID 1000 from source Application Error cannot be
found. Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
The following information was included with the event:
DTExec.exe
2005.90.3042.0
45cd7539
kernel32.dll
6.0.6000.16386
4549d328
e053534f
00000000000233ac
The substitution string for insert index (%1) could not be found"
I cant find anything online that enlightens me - I know that Vista needs SP
installed to work, so I've installed it:
@.@.Version= Microsoft SQL Server 2005 - 9.00.3054.00 (X64)
Mar 23 2007 18:41:50
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.0 (Build 6000: )
All the services are running under a domain user that has access to the
areas where the data is stored, both source and destination, so I'm hoping
it's not a permissions issue - if it is, I wouldnt know where to look.
I *could* copy a local database to the same server (renamed of course), so
it suggests that the server is largely OK - does this suggest it *is* a
permissions issue?
The domain user that the services are running under are not in the local
Administrators group, but they are in the
SQLServer2005MSSQLUser$MyComputer$MSSQLSERVER group - which I assume is the
group that was set up by the SQL Server Provisioning Tool for Vista.
This is a development machine so I frequently want to copy different
versions of different databases backwards and forwards.
Any suggestions? Any other Vista x64-ers out there?
Thanks in advance...
ChrisSQL Server uses Active Directory accounts and groups for its
permissions.
Active Directory accounts and groups are represented by GUIDs that are
unique to a particular Active Directory Domain which is run by a
Primary Domain Contoroller. If your new Vista machine is not part of
a network, or is on a different domain than the old one, then it
probably uses different GUIDs for the active directory accounts than
the source machine did. If you copied over the SQL Server database
using a backup, then you probably also copied all the old GUIDs for
the SQL Server accounts that point to the GUIDs on the old machine,
and not the ones on new machine.
This means that your SQL Server accounts are out of sync with active
directory. you may have to recreate your SQL Server accounts on the
new machine.
Permissions are assigned through SQL Server Management Studio in two
steps. First, you assign the active directory accounts that are
allowed to connect to a SQL Server instance. This is done by right
clicking the Logins folder under the Security folder of the SQL Server
instance the user is to connect to and selecting New Login.
Then, you assign what SQL Server instance users are allowed to connect
to a particular database within an instance. This is done by right
clicking the Security folder under the database you want to give
permission for and selecting New->user.
In both cases, an extensive permissions dialog will open. For the
Login folder, you only have to specify an active directory account.
For the Security folder, you have to click securables in the left
sidebar, add the entities you want to view (tables), and then set
select, reference, update, delete, and insert permissions. There are
more steps, but this should point you in the right direction.|||Andy, thanks for your reply...
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:1ee305c9-338f-4a4f-9a42-198b42c597b5@.w40g2000hsb.googlegroups.com...
> If your new Vista machine is not part of
> a network, or is on a different domain than the old one,
>
My new machine is part of the same Domain and is recognised within Active
Directory.
> Permissions are assigned through SQL Server Management Studio in two
> steps. First, you assign the active directory accounts that are
> allowed to connect to a SQL Server instance. This is done by right
> clicking the Logins folder under the Security folder of the SQL Server
> instance the user is to connect to and selecting New Login.
Each human administrator is per of an SQL Admins group as are each of the
domain users that the different servers run under. On each server, the SQL
Admins group is added with a login and has sufficiend permissions (AFAIK).
> Then, you assign what SQL Server instance users are allowed to connect
> to a particular database within an instance. This is done by right
> clicking the Security folder under the database you want to give
> permission for and selecting New->user.
>
Done
> In both cases, an extensive permissions dialog will open. For the
> Login folder, you only have to specify an active directory account.
> For the Security folder, you have to click securables in the left
> sidebar, add the entities you want to view (tables), and then set
> select, reference, update, delete, and insert permissions. There are
> more steps, but this should point you in the right direction.
>
The login is set as a sysdamin so surely this shouldnt be necessary?
Somewhere in my tweaking, I've changed something. I *think* it's for the
better - I'm still getting errors but I'm getting further along.
I'm now getting Error 12550: Access to the path
'\\MyServer\MyShare\MyDB.mdf' is denied. The SQL Admins group has read/write
permissions to this area so I'm puzzled.
This is immediately followed by another Error 12550: Object reference not
set to an instance of an object. There are other errors further on, but I
think they are just as a consequence of these earlier errors.
I'm actually going to start copying backups because I need to crack on with
things, but I'm determined to get to the bottom of this. In my work, this
wizard is very useful so I'd rather not have to work around it.
Any further ideas?
Cheers
Chrissqlsql
copy database wizard in cluster sql 2005
Hi all,
I have a issue when i tried to copy database from a machine with MSDE
database to a new sql 2005 cluster server. I could not copy it with copy
database wizard. Here is the message i got.
TITLE: Copy Database Wizard
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005
Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 .
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
Help.
Thanks,
MP
You probably ran into one of the more significant changes on clustering in
SQL 20005, the tools install. SQL 2005 tools are not installed to all
cluster nodes. You have to install to each node individually. Go to each
node and install the SQL 2005 client tools and you should be good to go.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Max" <Max@.discussions.microsoft.com> wrote in message
news:4B0044FE-CBD5-4426-9CBF-5FB13CD27A48@.microsoft.com...
> Hi all,
> I have a issue when i tried to copy database from a machine with MSDE
> database to a new sql 2005 cluster server. I could not copy it with copy
> database wizard. Here is the message i got.
> TITLE: Copy Database Wizard
> --
> The action you attempted to perform on a remote instance of SQL Server has
> failed because the action requires a SQL Server component that is not
> installed on the remote computer. To proceed, install SQL Server 2005
> Management Tools on the remote computer, and then try again. For more
> information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
> 2005
> Books Online, or find the article on MSDN at
> http://go.microsoft.com/fwlink/?LinkID=57083 .
> For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
> --
> Help.
> Thanks,
> MP
>
sqlsql
I have a issue when i tried to copy database from a machine with MSDE
database to a new sql 2005 cluster server. I could not copy it with copy
database wizard. Here is the message i got.
TITLE: Copy Database Wizard
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005
Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 .
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
Help.
Thanks,
MP
You probably ran into one of the more significant changes on clustering in
SQL 20005, the tools install. SQL 2005 tools are not installed to all
cluster nodes. You have to install to each node individually. Go to each
node and install the SQL 2005 client tools and you should be good to go.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Max" <Max@.discussions.microsoft.com> wrote in message
news:4B0044FE-CBD5-4426-9CBF-5FB13CD27A48@.microsoft.com...
> Hi all,
> I have a issue when i tried to copy database from a machine with MSDE
> database to a new sql 2005 cluster server. I could not copy it with copy
> database wizard. Here is the message i got.
> TITLE: Copy Database Wizard
> --
> The action you attempted to perform on a remote instance of SQL Server has
> failed because the action requires a SQL Server component that is not
> installed on the remote computer. To proceed, install SQL Server 2005
> Management Tools on the remote computer, and then try again. For more
> information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
> 2005
> Books Online, or find the article on MSDN at
> http://go.microsoft.com/fwlink/?LinkID=57083 .
> For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
> --
> Help.
> Thanks,
> MP
>
sqlsql
Tuesday, March 20, 2012
Copy Database Wizard
Hello, I am trying to copy my database tables and stored procedures to my local machine. I keep gettin gthis error
CDW Error Message
CDW Error Message
X "Your SQL Server Service is running under the local system account. You need to change you SQL Server Sevice account to have the rights to copy files over the network."
What do I do to correct this?
Thanks,
EricAre you working in a controlled environment ??
Active Directory and so ??
If that is so, you need to be system admin in the network to be able to copy those files ...|||The local System account only has permissions to run proggys on the local machine, to do any networkable actions the SQL Server needs to be run under an account that is able to have permissions added to it.
What You should do when createing or installing a SQL Server is to create another account for it to run under. If you are working in a domain You would create a domain account that is a member of the domain users group, and has the add permissions to log on as a service. Then increase the permissions as needed. Now if you want to use SQL Mail you need to do the above so that you can add a mail profile to the server so that the user can send emails (SQLServer mail uses the MAPI system same as Outlook).
If you are in a workgroup, create a local user and add the log on as service permissions. then on the other machines that it needs to talk to you would add the user.|||Is it at all possible to get instructions on how this can happen. Even if I have to uninstall Sql server and re-install it. I need to copy the Database to my local machine.|||Are you just trying to copy it once, or do you want this to be a regular job.
Copy Database Wizard
Hello at all,
I want to transfer sql2000 databases and DTS from machine to another; I have
tried to use "Copy Datebase Wizard", but I'm not sure this is the best
choice. Does anyone want to help me?
thank you
Thanks a lot.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>
|||Another question. what does occur if don't copy master database to target
machine?
Can I restore all DB with sql backup/restore utility? It's the same?
Thanks
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>
sqlsql
I want to transfer sql2000 databases and DTS from machine to another; I have
tried to use "Copy Datebase Wizard", but I'm not sure this is the best
choice. Does anyone want to help me?
thank you
Thanks a lot.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>
|||Another question. what does occur if don't copy master database to target
machine?
Can I restore all DB with sql backup/restore utility? It's the same?
Thanks
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>
sqlsql
Copy Database Wizard
Hello at all,
I want to transfer sql2000 databases and DTS from machine to another; I have
tried to use "Copy Datebase Wizard", but I'm not sure this is the best
choice. Does anyone want to help me?
thank youhi
see my blog
http://oneplace4sql.blogspot.com/
--
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"acolmano" <acolmano@.tin.it> wrote in message
news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
> Hello at all,
> I want to transfer sql2000 databases and DTS from machine to another; I
> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
> best choice. Does anyone want to help me?
> thank you|||Thanks a lot.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>> Hello at all,
>> I want to transfer sql2000 databases and DTS from machine to another; I
>> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
>> best choice. Does anyone want to help me?
>> thank you
>|||Another question. what does occur if don't copy master database to target
machine?
Can I restore all DB with sql backup/restore utility? It's the same?
Thanks
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>> Hello at all,
>> I want to transfer sql2000 databases and DTS from machine to another; I
>> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
>> best choice. Does anyone want to help me?
>> thank you
>|||Hi
You can restore master database restore backup cmd. Microsoft recomended way
is using sqlcmd tool
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
--
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"acolmano" <acolmano@.tin.it> wrote in message
news:eHwb62FnHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Another question. what does occur if don't copy master database to target
> machine?
> Can I restore all DB with sql backup/restore utility? It's the same?
> Thanks
>
> "vt" <vinu.t.1976@.gmail.com> wrote in message
> news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
>> hi
>> see my blog
>> http://oneplace4sql.blogspot.com/
>> --
>> VT
>> Knowledge is power, share it...
>> http://oneplace4sql.blogspot.com/
>> "acolmano" <acolmano@.tin.it> wrote in message
>> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>> Hello at all,
>> I want to transfer sql2000 databases and DTS from machine to another; I
>> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
>> best choice. Does anyone want to help me?
>> thank you
>>
>
I want to transfer sql2000 databases and DTS from machine to another; I have
tried to use "Copy Datebase Wizard", but I'm not sure this is the best
choice. Does anyone want to help me?
thank youhi
see my blog
http://oneplace4sql.blogspot.com/
--
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"acolmano" <acolmano@.tin.it> wrote in message
news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
> Hello at all,
> I want to transfer sql2000 databases and DTS from machine to another; I
> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
> best choice. Does anyone want to help me?
> thank you|||Thanks a lot.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>> Hello at all,
>> I want to transfer sql2000 databases and DTS from machine to another; I
>> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
>> best choice. Does anyone want to help me?
>> thank you
>|||Another question. what does occur if don't copy master database to target
machine?
Can I restore all DB with sql backup/restore utility? It's the same?
Thanks
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>> Hello at all,
>> I want to transfer sql2000 databases and DTS from machine to another; I
>> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
>> best choice. Does anyone want to help me?
>> thank you
>|||Hi
You can restore master database restore backup cmd. Microsoft recomended way
is using sqlcmd tool
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
--
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"acolmano" <acolmano@.tin.it> wrote in message
news:eHwb62FnHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Another question. what does occur if don't copy master database to target
> machine?
> Can I restore all DB with sql backup/restore utility? It's the same?
> Thanks
>
> "vt" <vinu.t.1976@.gmail.com> wrote in message
> news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
>> hi
>> see my blog
>> http://oneplace4sql.blogspot.com/
>> --
>> VT
>> Knowledge is power, share it...
>> http://oneplace4sql.blogspot.com/
>> "acolmano" <acolmano@.tin.it> wrote in message
>> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>> Hello at all,
>> I want to transfer sql2000 databases and DTS from machine to another; I
>> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
>> best choice. Does anyone want to help me?
>> thank you
>>
>
Copy Database Wizard
Hello at all,
I want to transfer sql2000 databases and DTS from machine to another; I have
tried to use "Copy Datebase Wizard", but I'm not sure this is the best
choice. Does anyone want to help me?
thank youhi
see my blog
http://oneplace4sql.blogspot.com/
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"acolmano" <acolmano@.tin.it> wrote in message
news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
> Hello at all,
> I want to transfer sql2000 databases and DTS from machine to another; I
> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
> best choice. Does anyone want to help me?
> thank you|||Thanks a lot.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>|||Another question. what does occur if don't copy master database to target
machine?
Can I restore all DB with sql backup/restore utility? It's the same?
Thanks
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>|||Hi
You can restore master database restore backup cmd. Microsoft recomended way
is using sqlcmd tool
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
--
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"acolmano" <acolmano@.tin.it> wrote in message
news:eHwb62FnHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Another question. what does occur if don't copy master database to target
> machine?
> Can I restore all DB with sql backup/restore utility? It's the same?
> Thanks
>
> "vt" <vinu.t.1976@.gmail.com> wrote in message
> news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
>
I want to transfer sql2000 databases and DTS from machine to another; I have
tried to use "Copy Datebase Wizard", but I'm not sure this is the best
choice. Does anyone want to help me?
thank youhi
see my blog
http://oneplace4sql.blogspot.com/
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"acolmano" <acolmano@.tin.it> wrote in message
news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
> Hello at all,
> I want to transfer sql2000 databases and DTS from machine to another; I
> have tried to use "Copy Datebase Wizard", but I'm not sure this is the
> best choice. Does anyone want to help me?
> thank you|||Thanks a lot.
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>|||Another question. what does occur if don't copy master database to target
machine?
Can I restore all DB with sql backup/restore utility? It's the same?
Thanks
"vt" <vinu.t.1976@.gmail.com> wrote in message
news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
> hi
> see my blog
> http://oneplace4sql.blogspot.com/
> --
> VT
> Knowledge is power, share it...
> http://oneplace4sql.blogspot.com/
> "acolmano" <acolmano@.tin.it> wrote in message
> news:OL37WlEnHHA.3952@.TK2MSFTNGP03.phx.gbl...
>|||Hi
You can restore master database restore backup cmd. Microsoft recomended way
is using sqlcmd tool
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
--
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"acolmano" <acolmano@.tin.it> wrote in message
news:eHwb62FnHHA.4196@.TK2MSFTNGP06.phx.gbl...
> Another question. what does occur if don't copy master database to target
> machine?
> Can I restore all DB with sql backup/restore utility? It's the same?
> Thanks
>
> "vt" <vinu.t.1976@.gmail.com> wrote in message
> news:eVmy20EnHHA.4424@.TK2MSFTNGP03.phx.gbl...
>
Subscribe to:
Posts (Atom)