Copy database from one server to a different server

Hi
I am trying to copy a database from one server to another using copy database wizard. However, in the process, I am receiving the following error message : 'Your Sql Server Service is running under the local system account. You need to change your sql server Service account to have the rights to copy files over the network.'
I have no idea how to handle this. Any help is greatly appreciated. Thanks in advance.Hi
You may want to check out alternative methods:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546
The service account seems can be found either the services applet or
Enterprise Manager.
John
"John" <john_si100@.yahoo.com> wrote in message
news:05CD7ACF-B765-468A-B9FD-BA501C286A89@.microsoft.com...
> Hi,
> I am trying to copy a database from one server to another using copy
database wizard. However, in the process, I am receiving the following error
message : 'Your Sql Server Service is running under the local system
account. You need to change your sql server Service account to have the
rights to copy files over the network.'
> I have no idea how to handle this. Any help is greatly appreciated. Thanks
in advance.|||Create a domain login for SQL Server... THen using SQL Enterprise Manager
right click your server-> Properties->Security and set the login and
password that you have just created...
Then give that NT login permissions on the appropriate files to do the copy
and you are done.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John" <john_si100@.yahoo.com> wrote in message
news:05CD7ACF-B765-468A-B9FD-BA501C286A89@.microsoft.com...
> Hi,
> I am trying to copy a database from one server to another using copy
database wizard. However, in the process, I am receiving the following error
message : 'Your Sql Server Service is running under the local system
account. You need to change your sql server Service account to have the
rights to copy files over the network.'
> I have no idea how to handle this. Any help is greatly appreciated. Thanks
in advance.

copy data from one database to another

Hi,
In our build process (where SQLServer is used as an embedded database) we always
recreate the database from scratch. When the database is recreated, the script
also recreates some basic data from the script.
Some of the QA folks are having a problem with this. They are not willing to lose all
of their existing data when a new build is invoked. I am trying to come with a simple
solution.
1. thr EM user will rename current database they have.
ALTER DATABASE OldName
MODIFY NAME = NewName
2. the build process will recreate the new database.
3. Now I need a tool to copy data from the old database. Since both old and new database
will
be in the same instance, a simple INSERT INTO TABLE(col1,col2,col3) select
col1,col2,col3
from olddatabase:table will do. What the tool should do is to disregard any dropped
columns
from being copied and set any new columns added in the newdatabase to null.
To perform step 3 is there a tool already available. I have a vague idea on how to write a
stored procedure for this, but I would prefer a tool already existing. Why reinvent the
wheel?
TIA
I think the easiest way to go about this is to use DTS. You can create a DTS
script that will do a straight copy from one database to another, specifying
which columns to skip.
|||"mmm" <mmm@.discussions.microsoft.com> wrote

>I think the easiest way to go about this is to use DTS. You can create a DTS
> script that will do a straight copy from one database to another, specifying
> which columns to skip.
The columns to skip should be automatic. I don't want to be editing DTS every
time.
I am thinking of writing a stored procedure in master database
which will use the following logic.
1. It will loop around every table of the target database where the data will go to.
2. For each table it will find out the columns and build a string as follows
INSERT INTO TARGET_DB.TABLE(COL LIST) SELECT COL_LIST
FROM SOURCE_DB.TABLE
Next the problem to tackle is the order of table. While poplating the tables
in step (1), it should populate all those tables first which either have no child tables
or child tables. That is, the sequence of loading the tables should not violate
PKY and FKY relationship.
Anyone knows a way to query tables in a database in required order mentioned above.
TIA

copy data from one database to another

Hi,
In our build process (where SQLServer is used as an embedded database) we al
ways
recreate the database from scratch. When the database is recreated, the scri
pt
also recreates some basic data from the script.
Some of the QA folks are having a problem with this. They are not willing to
lose all
of their existing data when a new build is invoked. I am trying to come with
a simple
solution.
1. thr EM user will rename current database they have.
ALTER DATABASE OldName
MODIFY NAME = NewName
2. the build process will recreate the new database.
3. Now I need a tool to copy data from the old database. Since both old and
new database
will
be in the same instance, a simple INSERT INTO TABLE(col1,col2,col3) select
col1,col2,col3
from olddatabase:table will do. What the tool should do is to disregard any
dropped
columns
from being copied and set any new columns added in the newdatabase to null.
To perform step 3 is there a tool already available. I have a vague idea on
how to write a
stored procedure for this, but I would prefer a tool already existing. Why r
einvent the
wheel?
TIAI think the easiest way to go about this is to use DTS. You can create a DTS
script that will do a straight copy from one database to another, specifying
which columns to skip.|||"mmm" <mmm@.discussions.microsoft.com> wrote

>I think the easiest way to go about this is to use DTS. You can create a DT
S
> script that will do a straight copy from one database to another, specifyi
ng
> which columns to skip.
The columns to skip should be automatic. I don't want to be editing DTS ever
y
time.
I am thinking of writing a stored procedure in master database
which will use the following logic.
1. It will loop around every table of the target database where the data wil
l go to.
2. For each table it will find out the columns and build a string as follows
INSERT INTO TARGET_DB.TABLE(COL LIST) SELECT COL_LIST
FROM SOURCE_DB.TABLE
Next the problem to tackle is the order of table. While poplating the tables
in step (1), it should populate all those tables first which either have no
child tables
or child tables. That is, the sequence of loading the tables should not viol
ate
PKY and FKY relationship.
Anyone knows a way to query tables in a database in required order mentioned
above.
TIA

copy data from one database to another

Hi,
In our build process (where SQLServer is used as an embedded database) we always
recreate the database from scratch. When the database is recreated, the script
also recreates some basic data from the script.
Some of the QA folks are having a problem with this. They are not willing to lose all
of their existing data when a new build is invoked. I am trying to come with a simple
solution.
1. thr EM user will rename current database they have.
ALTER DATABASE OldName
MODIFY NAME = NewName
2. the build process will recreate the new database.
3. Now I need a tool to copy data from the old database. Since both old and new database
will
be in the same instance, a simple INSERT INTO TABLE(col1,col2,col3) select
col1,col2,col3
from olddatabase:table will do. What the tool should do is to disregard any dropped
columns
from being copied and set any new columns added in the newdatabase to null.
To perform step 3 is there a tool already available. I have a vague idea on how to write a
stored procedure for this, but I would prefer a tool already existing. Why reinvent the
wheel?
TIAI think the easiest way to go about this is to use DTS. You can create a DTS
script that will do a straight copy from one database to another, specifying
which columns to skip.|||"mmm" <mmm@.discussions.microsoft.com> wrote
>I think the easiest way to go about this is to use DTS. You can create a DTS
> script that will do a straight copy from one database to another, specifying
> which columns to skip.
The columns to skip should be automatic. I don't want to be editing DTS every
time.
I am thinking of writing a stored procedure in master database
which will use the following logic.
1. It will loop around every table of the target database where the data will go to.
2. For each table it will find out the columns and build a string as follows
INSERT INTO TARGET_DB.TABLE(COL LIST) SELECT COL_LIST
FROM SOURCE_DB.TABLE
Next the problem to tackle is the order of table. While poplating the tables
in step (1), it should populate all those tables first which either have no child tables
or child tables. That is, the sequence of loading the tables should not violate
PKY and FKY relationship.
Anyone knows a way to query tables in a database in required order mentioned above.
TIA

Converting SQL Server 2000 database to 2005 format

Hello!
We have attached our 500GB SQL Server 2000 databases on 2005 server. The
process took literally took 10 seconds. I was wondering if databases should
undergo low level conversion when moved to 2005 environment in order to take
full advantage of new features. Will simply attaching the databases do the
job?
We are planning to switch databases to 9.0 compatibility mode. I am aware
certain features have been deprecated. Besides that I am concerned we won't
be able to take full advantage of new 2005 features unless we do low level
conversion. If this is the case, is there a way to initiate this process
after attaching the database ?
Any help is greatly appreciated,
IgorThere really is no low level conversion to take place. Most of the changes
are meta data and with the system and resource databases. It is highly
recommended that you run sp_updatestats after you attach it or better yet
after you set the mode to 9.0. Once you do that you will have full access
to the 2005 feature set.
Andrew J. Kelly SQL MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:OMvyLypLGHA.2216@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We have attached our 500GB SQL Server 2000 databases on 2005 server.
> The process took literally took 10 seconds. I was wondering if databases
> should undergo low level conversion when moved to 2005 environment in
> order to take full advantage of new features. Will simply attaching the
> databases do the job?
> We are planning to switch databases to 9.0 compatibility mode. I am aware
> certain features have been deprecated. Besides that I am concerned we
> won't be able to take full advantage of new 2005 features unless we do low
> level conversion. If this is the case, is there a way to initiate this
> process after attaching the database ?
> Any help is greatly appreciated,
> Igor
>|||Andrew,
Thanks a lot!
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:O1f2TcqLGHA.1760@.TK2MSFTNGP10.phx.gbl...
> There really is no low level conversion to take place. Most of the
> changes are meta data and with the system and resource databases. It is
> highly recommended that you run sp_updatestats after you attach it or
> better yet after you set the mode to 9.0. Once you do that you will have
> full access to the 2005 feature set.
>
> --
> Andrew J. Kelly SQL MVP
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:OMvyLypLGHA.2216@.TK2MSFTNGP09.phx.gbl...
>> Hello!
>> We have attached our 500GB SQL Server 2000 databases on 2005 server.
>> The process took literally took 10 seconds. I was wondering if databases
>> should undergo low level conversion when moved to 2005 environment in
>> order to take full advantage of new features. Will simply attaching the
>> databases do the job?
>> We are planning to switch databases to 9.0 compatibility mode. I am aware
>> certain features have been deprecated. Besides that I am concerned we
>> won't be able to take full advantage of new 2005 features unless we do
>> low level conversion. If this is the case, is there a way to initiate
>> this process after attaching the database ?
>> Any help is greatly appreciated,
>> Igor
>