If you're generating individual INSERT/VALUES statements, I wouldn't do that because it will take a month of Sundays to complete 1 million rows. In fact, most methods will not to mention the fact that such a thing will negate all possibility of minimal logging.
We need more information...
- Are you, indeed, generating individual INSERT/VALUES statements using the GUI method of scripting data?
- What does the CREATE TABLE statement look like for the target table?
- Does the target table already contain any rows or is it empty at the start of the deployment?
- Where will you be running this deployment script from? The command line or within SSMS?
- I'm assuming that the data for the deployment script will live in a file. Is that correct? If not, can it?
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)