![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
#3
| |||
| |||
|
|
Hello Matt, Where is the time being taken? All things being equal (Box Sizes, network Segment Speed, Resources available) the performance differences should not be dissimilar. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
#4
| |||
| |||
|
|
Hello Adam, the time is from the moment I press the start button to the moment the dialog box of successful transfer appears. The system is the same: on the same PC are installed SQL2000 and SQL2005, and for the test I used the same DB. First I exported a SQL2000 db to SQL2005, and it took its time. Then I exported the same db to the same SQL2000, with another name. I did the same with SQL2005 db, exporting it again to SQL2005 with another name. But the SQL2005 to SQL2005 took ages compared to the SQL2k to SQL2k. Any hint? Thanks, Mattia Hello Matt, Where is the time being taken? All things being equal (Box Sizes, network Segment Speed, Resources available) the performance differences should not be dissimilar. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
#5
| |||
| |||
|
|
Hello Matt, I was thinking more along the lines of the tables that are taking the time. Is this a restored 2K DB to 2K5? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, the time is from the moment I press the start button to the moment the dialog box of successful transfer appears. The system is the same: on the same PC are installed SQL2000 and SQL2005, and for the test I used the same DB. First I exported a SQL2000 db to SQL2005, and it took its time. Then I exported the same db to the same SQL2000, with another name. I did the same with SQL2005 db, exporting it again to SQL2005 with another name. But the SQL2005 to SQL2005 took ages compared to the SQL2k to SQL2k. Any hint? Thanks, Mattia Hello Matt, Where is the time being taken? All things being equal (Box Sizes, network Segment Speed, Resources available) the performance differences should not be dissimilar. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
#6
| |||
| |||
|
|
Hello Adam, Yes it seems that what it takes more is copying the lines between the two. The DB was originally in 2k, then I opened S2005 managenent studio, connected to the two servers, and exported the DB from the sql2k db to the sql2k5. Funny thing is that my webapplication ASP.NET 1.1, is much faster accessing the SQL2k5 db than the old SQL2k one. The only thing that I don't understand is this time it needs to export the same db with a different name on the same sql2k5 server. Best, Mattia On Mon, 4 Dec 2006 05:52:21 +0000 (UTC), Allan Mitchell allan (AT) no-spam (DOT) sqldts.com> wrote: Hello Matt, I was thinking more along the lines of the tables that are taking the time. Is this a restored 2K DB to 2K5? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, the time is from the moment I press the start button to the moment the dialog box of successful transfer appears. The system is the same: on the same PC are installed SQL2000 and SQL2005, and for the test I used the same DB. First I exported a SQL2000 db to SQL2005, and it took its time. Then I exported the same db to the same SQL2000, with another name. I did the same with SQL2005 db, exporting it again to SQL2005 with another name. But the SQL2005 to SQL2005 took ages compared to the SQL2k to SQL2k. Any hint? Thanks, Mattia Hello Matt, Where is the time being taken? All things being equal (Box Sizes, network Segment Speed, Resources available) the performance differences should not be dissimilar. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
#7
| |||
| |||
|
|
Hello Matt, Adam? Can you update the statistics on the source and destination DBs? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, Yes it seems that what it takes more is copying the lines between the two. The DB was originally in 2k, then I opened S2005 managenent studio, connected to the two servers, and exported the DB from the sql2k db to the sql2k5. Funny thing is that my webapplication ASP.NET 1.1, is much faster accessing the SQL2k5 db than the old SQL2k one. The only thing that I don't understand is this time it needs to export the same db with a different name on the same sql2k5 server. Best, Mattia On Mon, 4 Dec 2006 05:52:21 +0000 (UTC), Allan Mitchell allan (AT) no-spam (DOT) sqldts.com> wrote: Hello Matt, I was thinking more along the lines of the tables that are taking the time. Is this a restored 2K DB to 2K5? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, the time is from the moment I press the start button to the moment the dialog box of successful transfer appears. The system is the same: on the same PC are installed SQL2000 and SQL2005, and for the test I used the same DB. First I exported a SQL2000 db to SQL2005, and it took its time. Then I exported the same db to the same SQL2000, with another name. I did the same with SQL2005 db, exporting it again to SQL2005 with another name. But the SQL2005 to SQL2005 took ages compared to the SQL2k to SQL2k. Any hint? Thanks, Mattia Hello Matt, Where is the time being taken? All things being equal (Box Sizes, network Segment Speed, Resources available) the performance differences should not be dissimilar. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
#8
| |||
| |||
|
|
Hello Matt, Adam? Can you update the statistics on the source and destination DBs? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, Yes it seems that what it takes more is copying the lines between the two. The DB was originally in 2k, then I opened S2005 managenent studio, connected to the two servers, and exported the DB from the sql2k db to the sql2k5. Funny thing is that my webapplication ASP.NET 1.1, is much faster accessing the SQL2k5 db than the old SQL2k one. The only thing that I don't understand is this time it needs to export the same db with a different name on the same sql2k5 server. Best, Mattia On Mon, 4 Dec 2006 05:52:21 +0000 (UTC), Allan Mitchell allan (AT) no-spam (DOT) sqldts.com> wrote: Hello Matt, I was thinking more along the lines of the tables that are taking the time. Is this a restored 2K DB to 2K5? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, the time is from the moment I press the start button to the moment the dialog box of successful transfer appears. The system is the same: on the same PC are installed SQL2000 and SQL2005, and for the test I used the same DB. First I exported a SQL2000 db to SQL2005, and it took its time. Then I exported the same db to the same SQL2000, with another name. I did the same with SQL2005 db, exporting it again to SQL2005 with another name. But the SQL2005 to SQL2005 took ages compared to the SQL2k to SQL2k. Any hint? Thanks, Mattia Hello Matt, Where is the time being taken? All things being equal (Box Sizes, network Segment Speed, Resources available) the performance differences should not be dissimilar. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
#9
| |||
| |||
|
|
Hello Allan, I reinstalled everything and did the export test before installing SQL2005 SP1, ant it was fast. Now I reinstalled SP1, and is deadly slow. Now I'll go without SP1, but has anything like this happened to anyone? Thanks for your help anyway, Mattia On Mon, 4 Dec 2006 21:42:47 +0000 (UTC), Allan Mitchell allan (AT) no-spam (DOT) sqldts.com> wrote: Hello Matt, Adam? Can you update the statistics on the source and destination DBs? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, Yes it seems that what it takes more is copying the lines between the two. The DB was originally in 2k, then I opened S2005 managenent studio, connected to the two servers, and exported the DB from the sql2k db to the sql2k5. Funny thing is that my webapplication ASP.NET 1.1, is much faster accessing the SQL2k5 db than the old SQL2k one. The only thing that I don't understand is this time it needs to export the same db with a different name on the same sql2k5 server. Best, Mattia On Mon, 4 Dec 2006 05:52:21 +0000 (UTC), Allan Mitchell allan (AT) no-spam (DOT) sqldts.com> wrote: Hello Matt, I was thinking more along the lines of the tables that are taking the time. Is this a restored 2K DB to 2K5? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, the time is from the moment I press the start button to the moment the dialog box of successful transfer appears. The system is the same: on the same PC are installed SQL2000 and SQL2005, and for the test I used the same DB. First I exported a SQL2000 db to SQL2005, and it took its time. Then I exported the same db to the same SQL2000, with another name. I did the same with SQL2005 db, exporting it again to SQL2005 with another name. But the SQL2005 to SQL2005 took ages compared to the SQL2k to SQL2k. Any hint? Thanks, Mattia Hello Matt, Where is the time being taken? All things being equal (Box Sizes, network Segment Speed, Resources available) the performance differences should not be dissimilar. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
#10
| |||
| |||
|
|
Hello Matt, Ok so you updated the stats on the restored Db and then did the export before applying SP1 and then afterwards? The before export was fast and the after export was slow. Was the destination truncate prior to the second export? No I have not had anything like this happen to me. There is a CTP for SP2 out there so it may be worth you building a VPC and testing that as well. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Allan, I reinstalled everything and did the export test before installing SQL2005 SP1, ant it was fast. Now I reinstalled SP1, and is deadly slow. Now I'll go without SP1, but has anything like this happened to anyone? Thanks for your help anyway, Mattia On Mon, 4 Dec 2006 21:42:47 +0000 (UTC), Allan Mitchell allan (AT) no-spam (DOT) sqldts.com> wrote: Hello Matt, Adam? Can you update the statistics on the source and destination DBs? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, Yes it seems that what it takes more is copying the lines between the two. The DB was originally in 2k, then I opened S2005 managenent studio, connected to the two servers, and exported the DB from the sql2k db to the sql2k5. Funny thing is that my webapplication ASP.NET 1.1, is much faster accessing the SQL2k5 db than the old SQL2k one. The only thing that I don't understand is this time it needs to export the same db with a different name on the same sql2k5 server. Best, Mattia On Mon, 4 Dec 2006 05:52:21 +0000 (UTC), Allan Mitchell allan (AT) no-spam (DOT) sqldts.com> wrote: Hello Matt, I was thinking more along the lines of the tables that are taking the time. Is this a restored 2K DB to 2K5? Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello Adam, the time is from the moment I press the start button to the moment the dialog box of successful transfer appears. The system is the same: on the same PC are installed SQL2000 and SQL2005, and for the test I used the same DB. First I exported a SQL2000 db to SQL2005, and it took its time. Then I exported the same db to the same SQL2000, with another name. I did the same with SQL2005 db, exporting it again to SQL2005 with another name. But the SQL2005 to SQL2005 took ages compared to the SQL2k to SQL2k. Any hint? Thanks, Mattia Hello Matt, Where is the time being taken? All things being equal (Box Sizes, network Segment Speed, Resources available) the performance differences should not be dissimilar. Regards Allan Mitchell Konesans Ltd T +44 7966 476 572 F +44 2071 008 479 http://www.konesans.com Hello, this is what I'm trying to do: I have a database source2000 that I used to copy on the same sql2k (or other sql2k) server to dest2000 with Enterprise Manager import/export. Then I exported the source2000 in sql2k to source2005 in SQLServer 2005 using Management Studio. Now I'm trying to export source2005 to dest2005, both in SQLServer2005 with Export wizard of Management studio. This takes a lifetime, 10/20 more time than doing the same operation with Enterprise manager with sql2k. What am I doing wrong? Please don't suggest me to copy in other ways, this is the way I must use, because sometimes I copy only certain tables. Thanks, Mattia |
![]() |
| Thread Tools | |
| Display Modes | |
| |