Grant Fritchey (5/1/2016)
Jeff Moden (4/30/2016)
Grant Fritchey (4/28/2016)
Technical question:I want to export large amounts of data. However, I don't want to use SSIS. I'm going to use SQLCMD.EXE. I need to be able to script these exports so that I do, let's say, 10,000 rows at a time, in chunks. I'm doing this so that I have the ability to easily restart, and, allow for starting to migrate or move the exported files as each chunk finishes.
What's the best way to, in a relatively generic fashion, efficiently divide a table into these 10,000 row chunks?
Articles, blog posts, some documentation to get this going in the right direction. Please!
Oh, and, what the heck... URGENT!
Ha!
Ok, so based on some of the problems folks think you might have with chunking data, I'm curious. How many columns and how many rows do you want to export? And will they be delimited or fixed field?
It's going to be anything and everything. We're working on some automation for a tool at Redgate.
Can I take a moment to be a naysayer here?
"Anything and everything" is the quickest way to defeat. If a company tries to do too much at the same time on a project, the project is automatically doomed to failure either before or right after release time.
It's not that I want to sound pessimistic. It's just that from my perspective, the best way to start this tool is to define a specific start and end point for a specific line of data. Then once the first goal is met and validated, expand it to the other paths one at a time. I know that sounds annoying and like a lot of work, but if you narrow down the expectations for the first bit of work, you'll save yourself a lot of frustration and a possible giant failure at the starting sprint.