July 2, 2003 at 9:28 am
Okay, here's the problem. One of my users has a table she created and when is was finished loading, she had created 2 50G data files to support it. All data was char. The way things are done here, data files are broken down into 50G chunks with the last file able to grow, if needed.
She then went and added a datetime field on the end and populated with a character date from the table. There are approximately 187,500,000 records on the table. The second data file has grown to 185G and as of now says it has about 2G of free space. Can anyone tell me what is going on?
July 3, 2003 at 9:31 am
When you import the data into the DB, both the log file and data file will grow. You need to shrink them manually. Btw if your table considerably big, its good to spread it on multiple files in a file group and place on a different disk. The reason is when reading a table sql releases a single thread per file. Also place your data on file group and the index on another file group on different disks. This improves your performance and reduces the Disk I/O.
Shas3
July 3, 2003 at 10:07 am
Thanks. We're a small shop so we have no real experts and I am always looking for help.
July 3, 2003 at 10:28 am
Also setting your database Recovery mode to Simple will stop your log from growing. Since nothing is logged, you should backup before and after the import process. Read up on this before implementing to make sure it's acceptable to your business requirements first;)
Good Luck!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply