Re: DB size increase from SQL 2000 to 2005
- From: aj <ronald@xxxxxxxxxxxxx>
- Date: Mon, 25 Feb 2008 09:42:20 -0500
Erland Sommarskog wrote:
Artie (artie2269@xxxxxxxxx) writes:A few months ago a customer moved from SQL 2000 to SQL 2005. The db wasThere is very little information to work from. Have you checked the tables
backed up on SQL 2000 and restored to SQL 2005. The application using
this data works on SQL 2005 but takes no advantage of new features. The
db on SQL 2000 was about 2.9GB, now on SQL 2005, it is 16.5GB. The db
is set to Simple recovery so trx log is only 2mb. The mdf file is
16.5GB, Management Studio shows only 5mb free space. There has not been
a huge increase in transactions. One of the largest tables has only added 2,000 rows since the move to
SQL 2005. Yet the data and index size has jumped from about 400mb to
3.5 GB. I used the 'BigTables.sql' script found at various SQL sites: www.databasejournal.com/img/BigTables.sql
for fragmentation? How many rows are there in the table that has grown
so much? Are there text/ntext/image columns in the database? Does this
query return any rows:
SELECT object_name(object_id), name FROM sys.indexes
WHERE index_id = 0?
What does it mean and what should you do if this does return rows?
TIA
aj
.
- References:
- DB size increase from SQL 2000 to 2005
- From: Artie
- Re: DB size increase from SQL 2000 to 2005
- From: Erland Sommarskog
- DB size increase from SQL 2000 to 2005
- Prev by Date: Re: change structure of a simple query
- Next by Date: Need help with SQL Server Cluster
- Previous by thread: Re: DB size increase from SQL 2000 to 2005
- Next by thread: Re: DB size increase from SQL 2000 to 2005
- Index(es):
Relevant Pages
|
