The image data type holds variable-length binary data up to approx 2GB in size. The actual binary data is stored in a separate group of data pages to that which the table rows are stored in. A 16 byte pointer is then stored in the actual row that tells SQL Server where to find the data.
As the data is variable-length, it will only use as much space as it needs, ie a 2k image will only take 2k of storage space.
Thx for the input. The reason I asked was we have a db (which we use to store small images) that has grown to 1.5 gig. But there really is not enough data to account for this size.
I copied this db to my test env and ->
Deleted the data out of almost every table (except for seed data) and the db still remains .5 gig. I used delete from statements to remove the data from the tables
We have a copy of this same db with the same structure and seed data and its only 1000k.
I've run DBCC shrinkdatabase - but no luck.
Any one have any thoughts on why its so large - even after the removal of data?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.