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!

sqlsql

Copy Linked Server Password

Is there a way in SQL2005 to copy the linked server password from SQL2000?

We are about to copy our SQL 2000 database to SQL 2005 (and change operating systems and make other changes to the system). We can't do an upgrade in place because of the other changes, plus we want to have the original in case we can't get it updated before the start of business the next day.

I plan to move the databases by copying the files and attaching them, and I have a program that pulls users and encrypted passwords and adds them to the new system without encrypting the already encrypted passwords. Jobs I can script and run on the new system, DTS jobs I can open and save to the new system, and linked servers I can get the names of and link on the new server.

In SQL 2000 I would have "cheated" and copied the "DTS" and "Jobs" tables from one server to the other, but SQL 2005 has made it more complicated, so I will do it the slower way.

The problem comes with the linked server passwords. While I can see the linked server data in the master system tables, including the names and that there is an encrypted password. The problem is I don't know the passwords, so I can't enter it myself, and I can't update the system table, so I can't insert it as is. And sp_addlinkedsrvlogin does not have an option to not re-encrypt the password (like @.encryptopt = 'skip_encryption' in sp_addlogin).

Is there a way to figure out the password, or copy/insert the password without having it re-encrypt? In SQL2000 I would have done:

update A set
name = b.name,
password = b.password
from sysxlogins A, sysxlogins B
where A.srvid = 22
and B.srvid = 11

But SQL 2005 will not allow you to do this kind of update (allow updates has no effect).

Thanks, Tim

PS - Anything I might have missed that anyone can suggest, or any faster method of copying the database? We have a limited maintenance window to do this upgrade, so anything I can do ahead of time will help. Thanks again. Tim

Unfortunately, there is no supported method for doing this. You will have to recreate and respecify the passwords for those accounts.

Thanks
Laurentiu

|||Or, consider copying (backing up/restoring) everything to another machine and upgrading there from SQL Server 2000 to SQL Server 2005.

Copy Linked Server Password

Is there a way in SQL2005 to copy the linked server password from SQL2000?

We are about to copy our SQL 2000 database to SQL 2005 (and change operating systems and make other changes to the system). We can't do an upgrade in place because of the other changes, plus we want to have the original in case we can't get it updated before the start of business the next day.

I plan to move the databases by copying the files and attaching them, and I have a program that pulls users and encrypted passwords and adds them to the new system without encrypting the already encrypted passwords. Jobs I can script and run on the new system, DTS jobs I can open and save to the new system, and linked servers I can get the names of and link on the new server.

In SQL 2000 I would have "cheated" and copied the "DTS" and "Jobs" tables from one server to the other, but SQL 2005 has made it more complicated, so I will do it the slower way.

The problem comes with the linked server passwords. While I can see the linked server data in the master system tables, including the names and that there is an encrypted password. The problem is I don't know the passwords, so I can't enter it myself, and I can't update the system table, so I can't insert it as is. And sp_addlinkedsrvlogin does not have an option to not re-encrypt the password (like @.encryptopt = 'skip_encryption' in sp_addlogin).

Is there a way to figure out the password, or copy/insert the password without having it re-encrypt? In SQL2000 I would have done:

update A set
name = b.name,
password = b.password
from sysxlogins A, sysxlogins B
where A.srvid = 22
and B.srvid = 11

But SQL 2005 will not allow you to do this kind of update (allow updates has no effect).

Thanks, Tim

PS - Anything I might have missed that anyone can suggest, or any faster method of copying the database? We have a limited maintenance window to do this upgrade, so anything I can do ahead of time will help. Thanks again. Tim

Unfortunately, there is no supported method for doing this. You will have to recreate and respecify the passwords for those accounts.

Thanks
Laurentiu

|||Or, consider copying (backing up/restoring) everything to another machine and upgrading there from SQL Server 2000 to SQL Server 2005.

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

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

Copy Database Question

Setting up a sql2005 db server, trying to use Copy Database to move from sql2000 to sql2000.

When I use the copy database wizard it does copy the tables and logins but it does not appear to be copying the permissions (like db_datareader, db_datawriter, db_denydatareader, db_denydatawriter, etc.)

What could I be missing?

Thanks

i could never get Copy Database to work when migrating to 2005. i ended up detaching the database and copying the mdf to the new server and re-attaching.|||

The Copy DB wizard does not copy all metadata from one server to another. Check out this article:

http://msdn2.microsoft.com/en-us/library/ms188664.aspx

Specifically, this section that tells how to migrate everything else over:

Managing Metadata When Restoring to Another Server Instance

When you copy a database to another server instance, to provide a consistent experience to users and applications, you might have to re-create some or all of the metadata for the database, such as logins and jobs, on the other server instance. For more information, see Managing Metadata When Making a Database Available on Another Server Instance.

Thanks,
Sam Lester (MSFT)

Copy Database from SQL 2000 to SQL 2005

I'm trying to use "Copy Database" to copy a database from a SQL2000 instance
to a SQL2005 instance; everthing looks ok until I execute the operation and
get an error message on the action "Create Package" of "One or more
arguments are invalid (Copy Database Wizard)"
I've gone over it and over it and cannot see where the problem might be ...
TIA for any suggestions ..
LI would use SSIS for this instead of DTS
"Liz" <liz@.tiredofspam.com> wrote in message
news:e82zA%2346HHA.1164@.TK2MSFTNGP02.phx.gbl...
> I'm trying to use "Copy Database" to copy a database from a SQL2000
> instance to a SQL2005 instance; everthing looks ok until I execute the
> operation and get an error message on the action "Create Package" of "One
> or more arguments are invalid (Copy Database Wizard)"
> I've gone over it and over it and cannot see where the problem might be
> ...
> TIA for any suggestions ..
> L
>

copy database feature

Hello,
I am trying to use the copy database funtion from sql2000 to sql2005. It
fails miserably and logs only says:
step 0: The job failed. The Job was invoked by User domain\user. The last
step to run was step 1 (CDW_DBSERVERNAME_USERMACHINE_1_Step).
step 1: Executed as user: domain\user. The package execution failed. The
step failed.
There is no destination db already existing, the feature drop any database
on the destination server is activated, it fails at Execute SQL Server Agent
Job.
Although the database is created there is no tables created.
The user in the source and destination server is the same for the sql
service and the agent.
I am a bit lost. Is ity possible to do that between sql2k and sql2k5?
Thanks for the help
Wilfrid
If you are copying the whole db why not just restore from a full backup of
the 2000 db on 2005?
Andrew J. Kelly SQL MVP
"Wilfrid" <grille11@.yahoo.com> wrote in message
news:4399b19d$0$22164$afc38c87@.news.easynet.fr...
> Hello,
> I am trying to use the copy database funtion from sql2000 to sql2005. It
> fails miserably and logs only says:
> step 0: The job failed. The Job was invoked by User domain\user. The
> last step to run was step 1 (CDW_DBSERVERNAME_USERMACHINE_1_Step).
> step 1: Executed as user: domain\user. The package execution failed. The
> step failed.
> There is no destination db already existing, the feature drop any database
> on the destination server is activated, it fails at Execute SQL Server
> Agent Job.
> Although the database is created there is no tables created.
> The user in the source and destination server is the same for the sql
> service and the agent.
> I am a bit lost. Is ity possible to do that between sql2k and sql2k5?
> Thanks for the help
> Wilfrid
>
|||The process of dumping a db from one server and then restore it to another server takes longer than just using a feature
available form sql2k5.
I was using, with sql2k, the exporting objects functionnality from one server to another but this feature is not
available anymore with sql 2k5 and I believe it has been replaced with the copy db.
Andrew J. Kelly wrote:
> If you are copying the whole db why not just restore from a full backup of
> the 2000 db on 2005?
>
|||The copy db functionality was available in 200 as well and is not new. But
it is usually not faster or cleaner than a backup and restore. You should
already be doing regular backups so all you have to do is issue the restore.
You don't even have to copy the file first. As long as the folder is
accessible from the other server you can restore directly from there.
Andrew J. Kelly SQL MVP
"grille11" <grille11@.yahoo.com> wrote in message
news:439b429e$0$22164$afc38c87@.news.easynet.fr...[vbcol=seagreen]
> The process of dumping a db from one server and then restore it to another
> server takes longer than just using a feature available form sql2k5.
> I was using, with sql2k, the exporting objects functionnality from one
> server to another but this feature is not available anymore with sql 2k5
> and I believe it has been replaced with the copy db.
>
> Andrew J. Kelly wrote:

copy database feature

Hello,
I am trying to use the copy database funtion from sql2000 to sql2005. It
fails miserably and logs only says:
step 0: The job failed. The Job was invoked by User domain\user. The last
step to run was step 1 (CDW_DBSERVERNAME_USERMACHINE_1_Step).
step 1: Executed as user: domain\user. The package execution failed. The
step failed.
There is no destination db already existing, the feature drop any database
on the destination server is activated, it fails at Execute SQL Server Agent
Job.
Although the database is created there is no tables created.
The user in the source and destination server is the same for the sql
service and the agent.
I am a bit lost. Is ity possible to do that between sql2k and sql2k5?
Thanks for the help
WilfridIf you are copying the whole db why not just restore from a full backup of
the 2000 db on 2005?
Andrew J. Kelly SQL MVP
"Wilfrid" <grille11@.yahoo.com> wrote in message
news:4399b19d$0$22164$afc38c87@.news.easynet.fr...
> Hello,
> I am trying to use the copy database funtion from sql2000 to sql2005. It
> fails miserably and logs only says:
> step 0: The job failed. The Job was invoked by User domain\user. The
> last step to run was step 1 (CDW_DBSERVERNAME_USERMACHINE_1_Step).
> step 1: Executed as user: domain\user. The package execution failed. The
> step failed.
> There is no destination db already existing, the feature drop any database
> on the destination server is activated, it fails at Execute SQL Server
> Agent Job.
> Although the database is created there is no tables created.
> The user in the source and destination server is the same for the sql
> service and the agent.
> I am a bit lost. Is ity possible to do that between sql2k and sql2k5?
> Thanks for the help
> Wilfrid
>|||The process of dumping a db from one server and then restore it to another s
erver takes longer than just using a feature
available form sql2k5.
I was using, with sql2k, the exporting objects functionnality from one serve
r to another but this feature is not
available anymore with sql 2k5 and I believe it has been replaced with the c
opy db.
Andrew J. Kelly wrote:
> If you are copying the whole db why not just restore from a full backup of
> the 2000 db on 2005?
>|||The copy db functionality was available in 200 as well and is not new. But
it is usually not faster or cleaner than a backup and restore. You should
already be doing regular backups so all you have to do is issue the restore.
You don't even have to copy the file first. As long as the folder is
accessible from the other server you can restore directly from there.
Andrew J. Kelly SQL MVP
"grille11" <grille11@.yahoo.com> wrote in message
news:439b429e$0$22164$afc38c87@.news.easynet.fr...[vbcol=seagreen]
> The process of dumping a db from one server and then restore it to another
> server takes longer than just using a feature available form sql2k5.
> I was using, with sql2k, the exporting objects functionnality from one
> server to another but this feature is not available anymore with sql 2k5
> and I believe it has been replaced with the copy db.
>
> Andrew J. Kelly wrote:

copy database feature

Hello,
I am trying to use the copy database funtion from sql2000 to sql2005. It
fails miserably and logs only says:
step 0: The job failed. The Job was invoked by User domain\user. The last
step to run was step 1 (CDW_DBSERVERNAME_USERMACHINE_1_Step).
step 1: Executed as user: domain\user. The package execution failed. The
step failed.
There is no destination db already existing, the feature drop any database
on the destination server is activated, it fails at Execute SQL Server Agent
Job.
Although the database is created there is no tables created.
The user in the source and destination server is the same for the sql
service and the agent.
I am a bit lost. Is ity possible to do that between sql2k and sql2k5?
Thanks for the help
WilfridIf you are copying the whole db why not just restore from a full backup of
the 2000 db on 2005?
--
Andrew J. Kelly SQL MVP
"Wilfrid" <grille11@.yahoo.com> wrote in message
news:4399b19d$0$22164$afc38c87@.news.easynet.fr...
> Hello,
> I am trying to use the copy database funtion from sql2000 to sql2005. It
> fails miserably and logs only says:
> step 0: The job failed. The Job was invoked by User domain\user. The
> last step to run was step 1 (CDW_DBSERVERNAME_USERMACHINE_1_Step).
> step 1: Executed as user: domain\user. The package execution failed. The
> step failed.
> There is no destination db already existing, the feature drop any database
> on the destination server is activated, it fails at Execute SQL Server
> Agent Job.
> Although the database is created there is no tables created.
> The user in the source and destination server is the same for the sql
> service and the agent.
> I am a bit lost. Is ity possible to do that between sql2k and sql2k5?
> Thanks for the help
> Wilfrid
>|||The process of dumping a db from one server and then restore it to another server takes longer than just using a feature
available form sql2k5.
I was using, with sql2k, the exporting objects functionnality from one server to another but this feature is not
available anymore with sql 2k5 and I believe it has been replaced with the copy db.
Andrew J. Kelly wrote:
> If you are copying the whole db why not just restore from a full backup of
> the 2000 db on 2005?
>|||The copy db functionality was available in 200 as well and is not new. But
it is usually not faster or cleaner than a backup and restore. You should
already be doing regular backups so all you have to do is issue the restore.
You don't even have to copy the file first. As long as the folder is
accessible from the other server you can restore directly from there.
--
Andrew J. Kelly SQL MVP
"grille11" <grille11@.yahoo.com> wrote in message
news:439b429e$0$22164$afc38c87@.news.easynet.fr...
> The process of dumping a db from one server and then restore it to another
> server takes longer than just using a feature available form sql2k5.
> I was using, with sql2k, the exporting objects functionnality from one
> server to another but this feature is not available anymore with sql 2k5
> and I believe it has been replaced with the copy db.
>
> Andrew J. Kelly wrote:
>> If you are copying the whole db why not just restore from a full backup
>> of the 2000 db on 2005?

Copy and Paste multiple-line text directly in results pane

In SQL2005, I was trying to copy multiple-line text from notepad and paste it into SQL results pane to modify the data directly. But I could only write the first line into the database.

I used to do this in SQL7. It worked fine. Now we just converted the system to SQL2005. This functionality seems to be gone. Is that true? Can somebody confirm this or give out the solution of this issue?

Thanks.

Nobody answers? Please ...

Thanks.

Copy and Paste multiple-line text directly in results pane

In SQL2005, I was trying to copy multiple-line text from notepad and paste it into SQL results pane to modify the data directly. But I could only write the first line into the database.

I used to do this in SQL7. It worked fine. Now we just converted the system to SQL2005. This functionality seems to be gone. Is that true? Can somebody confirm this or give out the solution of this issue?

Thanks.

Nobody answers? Please ...

Thanks.

copy a table with sql2005

Using managment studio, how can i copy a table and his records, from a
server (2005) to another server (express) ?
I know how to create a script with table structure, but not with data into..
thanks
MauroSome options here: http://www.karaszi.com/SQLServer/info_generate_script.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mauro Miotello" <sviluppo@.ashnet.it> wrote in message news:e1k0kk$9q2$1@.nnrp.ngi.it...
> Using managment studio, how can i copy a table and his records, from a
> server (2005) to another server (express) ?
> I know how to create a script with table structure, but not with data into..
> thanks
> Mauro
>

copy a table with sql2005

Using managment studio, how can i copy a table and his records, from a
server (2005) to another server (express) ?
I know how to create a script with table structure, but not with data into..
thanks
MauroSome options here: http://www.karaszi.com/SQLServer/in...rate_script.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Mauro Miotello" <sviluppo@.ashnet.it> wrote in message news:e1k0kk$9q2$1@.nnrp.ngi.it...[vbco
l=seagreen]
> Using managment studio, how can i copy a table and his records, from a
> server (2005) to another server (express) ?
> I know how to create a script with table structure, but not with data into
.
> thanks
> Mauro
>[/vbcol]

Converting SQL2000 database to SQL2005

Are there any stored procedures that have to be run on a database when
restoring from SQL2000 to SQL 2005? If so, which ones?
Many Thanks!
No. But you should probably run the Upgrade Advisor (found on the SQL 2005
distribution media) before moving the database over, in order to ensure that
at least most of your code is compatible (the Advisor won't find
everything).

Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Steve" <stevex2@.directcon.net> wrote in message
news:CD8A547F-7754-4FBB-9B6E-29C3B4AECB5C@.microsoft.com...
> Are there any stored procedures that have to be run on a database when
> restoring from SQL2000 to SQL 2005? If so, which ones?
> Many Thanks!
|||And also up date compatibility mode when you are ready for it (see sp_dbcmptlevel).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam Machanic" <amachanic@.IHATESPAMgmail.com> wrote in message
news:53A849D2-97E5-4ACE-A1DB-5EFC798026AF@.microsoft.com...
> No. But you should probably run the Upgrade Advisor (found on the SQL 2005 distribution media)
> before moving the database over, in order to ensure that at least most of your code is compatible
> (the Advisor won't find everything).
>
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Steve" <stevex2@.directcon.net> wrote in message
> news:CD8A547F-7754-4FBB-9B6E-29C3B4AECB5C@.microsoft.com...
>

Converting SQL2000 database to SQL2005

Are there any stored procedures that have to be run on a database when
restoring from SQL2000 to SQL 2005? If so, which ones?
Many Thanks!No. But you should probably run the Upgrade Advisor (found on the SQL 2005
distribution media) before moving the database over, in order to ensure that
at least most of your code is compatible (the Advisor won't find
everything).
Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Steve" <stevex2@.directcon.net> wrote in message
news:CD8A547F-7754-4FBB-9B6E-29C3B4AECB5C@.microsoft.com...
> Are there any stored procedures that have to be run on a database when
> restoring from SQL2000 to SQL 2005? If so, which ones?
> Many Thanks!|||And also up date compatibility mode when you are ready for it (see sp_dbcmptlevel).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam Machanic" <amachanic@.IHATESPAMgmail.com> wrote in message
news:53A849D2-97E5-4ACE-A1DB-5EFC798026AF@.microsoft.com...
> No. But you should probably run the Upgrade Advisor (found on the SQL 2005 distribution media)
> before moving the database over, in order to ensure that at least most of your code is compatible
> (the Advisor won't find everything).
>
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Steve" <stevex2@.directcon.net> wrote in message
> news:CD8A547F-7754-4FBB-9B6E-29C3B4AECB5C@.microsoft.com...
>> Are there any stored procedures that have to be run on a database when
>> restoring from SQL2000 to SQL 2005? If so, which ones?
>> Many Thanks!
>

Converting SQL2000 database to SQL2005

Are there any stored procedures that have to be run on a database when
restoring from SQL2000 to SQL 2005? If so, which ones?
Many Thanks!No. But you should probably run the Upgrade Advisor (found on the SQL 2005
distribution media) before moving the database over, in order to ensure that
at least most of your code is compatible (the Advisor won't find
everything).
Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Steve" <stevex2@.directcon.net> wrote in message
news:CD8A547F-7754-4FBB-9B6E-29C3B4AECB5C@.microsoft.com...
> Are there any stored procedures that have to be run on a database when
> restoring from SQL2000 to SQL 2005? If so, which ones?
> Many Thanks!|||And also up date compatibility mode when you are ready for it (see sp_dbcmpt
level).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam Machanic" <amachanic@.IHATESPAMgmail.com> wrote in message
news:53A849D2-97E5-4ACE-A1DB-5EFC798026AF@.microsoft.com...
> No. But you should probably run the Upgrade Advisor (found on the SQL 200
5 distribution media)
> before moving the database over, in order to ensure that at least most of
your code is compatible
> (the Advisor won't find everything).
>
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Steve" <stevex2@.directcon.net> wrote in message
> news:CD8A547F-7754-4FBB-9B6E-29C3B4AECB5C@.microsoft.com...
>