December 15, 2014 at 9:17 am
I'm wondering if someone didn't corrupt the file(xls) and change the column types. Have you tried creating a new xls template for importing. Is everyone having problems with import or just certain computers/individuals.
Tom
December 26, 2014 at 11:02 am
To be sure, make SQL update the page (and row) usage counts and see if there are any large discrepancies:
DBCC UPDATEUSAGE ( '<your_db_name>' )
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
January 2, 2015 at 4:56 am
jumping in late on this one and sorry if this has been covered already. I read recently about free space in heaps (tables without a clustered index). Apparently SQL never releases the space back from the table to the database during updates and deletes and instead uses an internal pointer system to let SQL know where to find records. here[/url]is a link to Brent Ozar page, have a look at the Captive pages part.
If you are doing these bulk inserts into the same heaps this could be your reason. I am unsure (as it doesn't mention in the article nor have i tested it myself) on what affect this has on free space statistics fed back from SQL, but it could well be worth a look into if you are using heaps.
John
January 14, 2015 at 4:39 am
ScottPletcher (12/26/2014)
To be sure, make SQL update the page (and row) usage counts and see if there are any large discrepancies:
DBCC UPDATEUSAGE ( '<your_db_name>' )
I did this, the pages were updated but the size did'nt change.
Any idea?
January 14, 2015 at 4:43 am
I will try to backup and restore this db.
Lets see if this will work.
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply