Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/

edited May 23, 2017 at 12:40

edited May 23, 2017 at 12:40

I'm not a DBA/DBMS guru, so just some ideas:

Turn off indexes on tData2 during the migration.
Do it in smaller chunks for smaller transaction log. (Batch commit on large INSERT operation in native SQL? Batch commit on large INSERT operation in native SQL?, How to implement LIMIT with Microsoft SQL Server? How to implement LIMIT with Microsoft SQL Server?)
Make sure that [tData].[Key] has an index.
I'd consider replacing the subselect with a join if it's possible at all.

I'm not a DBA/DBMS guru, so just some ideas:

Turn off indexes on tData2 during the migration.
Do it in smaller chunks for smaller transaction log. (Batch commit on large INSERT operation in native SQL?, How to implement LIMIT with Microsoft SQL Server?)
Make sure that [tData].[Key] has an index.
I'd consider replacing the subselect with a join if it's possible at all.

I'm not a DBA/DBMS guru, so just some ideas:

Turn off indexes on tData2 during the migration.
Do it in smaller chunks for smaller transaction log. (Batch commit on large INSERT operation in native SQL?, How to implement LIMIT with Microsoft SQL Server?)
Make sure that [tData].[Key] has an index.
I'd consider replacing the subselect with a join if it's possible at all.

added 24 characters in body

edited Jul 19, 2012 at 9:32

edited Jul 19, 2012 at 9:32

I'm not a DBA/DBMS guru, so just some ideas:

Turn off indexes on tData2 during the migration.
Do it in smaller chunks for smaller transaction log. (Batch commit on large INSERT operation in native SQL?, How to implement LIMIT with Microsoft SQL Server?)
Make sure that [tData].[Key] has an index.
I'd consider replacing the subselect with a join if it's possible at all.

I'm not a DBA/DBMS guru, so just some ideas:

Turn off indexes on tData2 during the migration.
Do it in smaller chunks for smaller transaction log. (Batch commit on large INSERT operation in native SQL?, How to implement LIMIT with Microsoft SQL Server?)
Make sure that [tData].[Key] has an index.
I'd consider replacing the subselect with a join.

I'm not a DBA/DBMS guru, so just some ideas:

Turn off indexes on tData2 during the migration.
Do it in smaller chunks for smaller transaction log. (Batch commit on large INSERT operation in native SQL?, How to implement LIMIT with Microsoft SQL Server?)
Make sure that [tData].[Key] has an index.
I'd consider replacing the subselect with a join if it's possible at all.

answered Jul 18, 2012 at 20:59

answered Jul 18, 2012 at 20:59

I'm not a DBA/DBMS guru, so just some ideas:

Turn off indexes on tData2 during the migration.
Do it in smaller chunks for smaller transaction log. (Batch commit on large INSERT operation in native SQL?, How to implement LIMIT with Microsoft SQL Server?)
Make sure that [tData].[Key] has an index.
I'd consider replacing the subselect with a join.

lang-sql