dbTalk Databases Forums  

SQL2000 and SQL2005 export speed

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss SQL2000 and SQL2005 export speed in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Matt
 
Posts: n/a

Default SQL2000 and SQL2005 export speed - 12-01-2006 , 05:09 AM






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


Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-03-2006 , 03:43 AM






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

Quote:
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



Reply With Quote
  #3  
Old   
Matt
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-03-2006 , 06:43 PM



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


Quote:
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



Reply With Quote
  #4  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-03-2006 , 11:52 PM



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

Quote:
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



Reply With Quote
  #5  
Old   
Matt
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-04-2006 , 05:24 AM



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:

Quote:
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



Reply With Quote
  #6  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-04-2006 , 03:42 PM



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

Quote:
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



Reply With Quote
  #7  
Old   
Matt
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-05-2006 , 08:08 AM



Hi Allan,

sorry I've mistaken your name.
I tried to update, and I received a lot of:

Updating [dbo].[ACMG_Eventi]
0 index(es)/statistic(s) have been updated, 0 did not require
update.

Updating [dbo].[ACMG_EventiAccessiQuote]
0 index(es)/statistic(s) have been updated, 0 did not require
update.

Updating [dbo].[ACMG_EventiECM]
0 index(es)/statistic(s) have been updated, 0 did not require
update.
.....ecc

No table required the update.

I made other tests, and everytime is the same: exporting between two
databases in sql2005 takes much more time than exporting between two
sql2000 (Same DBs, same computer).

Thank you 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:

Quote:
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



Reply With Quote
  #8  
Old   
Matt
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-10-2006 , 09:33 AM



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:

Quote:
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



Reply With Quote
  #9  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-10-2006 , 09:43 AM



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

Quote:
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



Reply With Quote
  #10  
Old   
Matt
 
Posts: n/a

Default Re: SQL2000 and SQL2005 export speed - 12-10-2006 , 05:40 PM



Hello Allan,

what I exactly did is:

- machine with SQl2000 SP4 and SQL2005 SP1 installed
- uninstalled SQL2005
- reinstalled SQL2005
- run management studio and exported the MYDB from the SQL2000
instance on the same machine to the newly created SLQ2005
- updated stats, checked compatibilty
- exported MYDB in SQL2005 to MYDB2 in SQL2005 -> fast
- installed SQL2005SP1
- exported MYDB in SQL2005 to MYDB3 in SQL2005 -> insanely slow

I can live without SP1 in my development machine, but I'm curious to
know what SP1 is doing for making everything slower.

Thanks,
Mattia


On Sun, 10 Dec 2006 15:43:45 +0000 (UTC), Allan Mitchell
<allan (AT) no-spam (DOT) sqldts.com> wrote:

Quote:
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



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.