Rough estimate of Database Size

We are running a Finance System using SQL Server 2000. The production
database is around 20GB in size.
Since the system supports SQL Server 2005 and we are going to replace the
existing server, we would like to use SQL Server 2005 as backend database.
As we are in the sizing stage, we would like to get an estimate of the
database with SQL Server 2005.
We would like to know is there any way to find out the size of the
corresponding SQL server 2005 database. We would also like to know what
factors affect the size of database ? Is there any special feature in SQL
Server 2005 takes up more space ?
ThanksPeter
Don't you perfrom some monitoring such as how often your DB was growing?
What does the appliaction do more INSERTS/UPDATE/DELETE or SELECTs?
Well I know it is hard to get on right target , so create the database with
max estimated size and don't use Automatically autogrow file feature. It is
very important especially for LOG file as it grows much more often than
DATA file. Use filegrowth in megabytes feature ,something like 500 MB or 1GB
For SQL Server 2005 there is 'instant file initialization' feature( for
data files only) . Make sure that SQL Server account is added to Perform
volume Maintenance Task
http://support.microsoft.com/kb/931843
http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:eVypU0V6HHA.5212@.TK2MSFTNGP04.phx.gbl...
> We are running a Finance System using SQL Server 2000. The production
> database is around 20GB in size.
> Since the system supports SQL Server 2005 and we are going to replace the
> existing server, we would like to use SQL Server 2005 as backend database.
> As we are in the sizing stage, we would like to get an estimate of the
> database with SQL Server 2005.
> We would like to know is there any way to find out the size of the
> corresponding SQL server 2005 database. We would also like to know what
> factors affect the size of database ? Is there any special feature in SQL
> Server 2005 takes up more space ?
> Thanks
>|||Dear Uri,
The database has around 100 insert / update transactions a day. The others
just perform read only.
Does index structure in SQL Server 2000 is different from that from SQL
Server 2005 ?
Thanks
Peter
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eLtsDDW6HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Peter
> Don't you perfrom some monitoring such as how often your DB was growing?
> What does the appliaction do more INSERTS/UPDATE/DELETE or SELECTs?
> Well I know it is hard to get on right target , so create the database
> with max estimated size and don't use Automatically autogrow file
> feature. It is very important especially for LOG file as it grows much
> more often than DATA file. Use filegrowth in megabytes feature ,something
> like 500 MB or 1GB
> For SQL Server 2005 there is 'instant file initialization' feature( for
> data files only) . Make sure that SQL Server account is added to Perform
> volume Maintenance Task
> http://support.microsoft.com/kb/931843
> http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
> http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx
> "Peter" <Peter@.discussions.microsoft.com> wrote in message
> news:eVypU0V6HHA.5212@.TK2MSFTNGP04.phx.gbl...
>> We are running a Finance System using SQL Server 2000. The production
>> database is around 20GB in size.
>> Since the system supports SQL Server 2005 and we are going to replace the
>> existing server, we would like to use SQL Server 2005 as backend
>> database.
>> As we are in the sizing stage, we would like to get an estimate of the
>> database with SQL Server 2005.
>> We would like to know is there any way to find out the size of the
>> corresponding SQL server 2005 database. We would also like to know what
>> factors affect the size of database ? Is there any special feature in
>> SQL Server 2005 takes up more space ?
>> Thanks
>|||Peter
> Does index structure in SQL Server 2000 is different from that from SQL
> Server 2005 ?
No
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:%23xO2eNW6HHA.3940@.TK2MSFTNGP05.phx.gbl...
> Dear Uri,
> The database has around 100 insert / update transactions a day. The
> others just perform read only.
> Does index structure in SQL Server 2000 is different from that from SQL
> Server 2005 ?
> Thanks
> Peter
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eLtsDDW6HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Peter
>> Don't you perfrom some monitoring such as how often your DB was growing?
>> What does the appliaction do more INSERTS/UPDATE/DELETE or SELECTs?
>> Well I know it is hard to get on right target , so create the database
>> with max estimated size and don't use Automatically autogrow file
>> feature. It is very important especially for LOG file as it grows much
>> more often than DATA file. Use filegrowth in megabytes feature ,something
>> like 500 MB or 1GB
>> For SQL Server 2005 there is 'instant file initialization' feature( for
>> data files only) . Make sure that SQL Server account is added to Perform
>> volume Maintenance Task
>> http://support.microsoft.com/kb/931843
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx
>> "Peter" <Peter@.discussions.microsoft.com> wrote in message
>> news:eVypU0V6HHA.5212@.TK2MSFTNGP04.phx.gbl...
>> We are running a Finance System using SQL Server 2000. The production
>> database is around 20GB in size.
>> Since the system supports SQL Server 2005 and we are going to replace
>> the existing server, we would like to use SQL Server 2005 as backend
>> database.
>> As we are in the sizing stage, we would like to get an estimate of the
>> database with SQL Server 2005.
>> We would like to know is there any way to find out the size of the
>> corresponding SQL server 2005 database. We would also like to know what
>> factors affect the size of database ? Is there any special feature in
>> SQL Server 2005 takes up more space ?
>> Thanks
>>
>|||You can use your existing SQL Server 2000 database as a good estimate of
2005 space requirements. The new features that come to mind that will
affect space are vardecimal and included index columns. Tempdb space may
need to be significantly larger, depending on the features you use. See
http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx.
Hope this helps.
Dan Guzman
SQL Server MVP
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:eVypU0V6HHA.5212@.TK2MSFTNGP04.phx.gbl...
> We are running a Finance System using SQL Server 2000. The production
> database is around 20GB in size.
> Since the system supports SQL Server 2005 and we are going to replace the
> existing server, we would like to use SQL Server 2005 as backend database.
> As we are in the sizing stage, we would like to get an estimate of the
> database with SQL Server 2005.
> We would like to know is there any way to find out the size of the
> corresponding SQL server 2005 database. We would also like to know what
> factors affect the size of database ? Is there any special feature in SQL
> Server 2005 takes up more space ?
> Thanks
>|||Isn't instant file initialization an Enterprise Edition only feature?
TheSQLGuru
President
Indicium Resources, Inc.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eLtsDDW6HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Peter
> Don't you perfrom some monitoring such as how often your DB was growing?
> What does the appliaction do more INSERTS/UPDATE/DELETE or SELECTs?
> Well I know it is hard to get on right target , so create the database
> with max estimated size and don't use Automatically autogrow file
> feature. It is very important especially for LOG file as it grows much
> more often than DATA file. Use filegrowth in megabytes feature ,something
> like 500 MB or 1GB
> For SQL Server 2005 there is 'instant file initialization' feature( for
> data files only) . Make sure that SQL Server account is added to Perform
> volume Maintenance Task
> http://support.microsoft.com/kb/931843
> http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
> http://www.microsoft.com/technet/prodtechnol/sql/2005/workingwithtempdb.mspx
> "Peter" <Peter@.discussions.microsoft.com> wrote in message
> news:eVypU0V6HHA.5212@.TK2MSFTNGP04.phx.gbl...
>> We are running a Finance System using SQL Server 2000. The production
>> database is around 20GB in size.
>> Since the system supports SQL Server 2005 and we are going to replace the
>> existing server, we would like to use SQL Server 2005 as backend
>> database.
>> As we are in the sizing stage, we would like to get an estimate of the
>> database with SQL Server 2005.
>> We would like to know is there any way to find out the size of the
>> corresponding SQL server 2005 database. We would also like to know what
>> factors affect the size of database ? Is there any special feature in
>> SQL Server 2005 takes up more space ?
>> Thanks
>|||On Tue, 28 Aug 2007 14:20:06 +0300, "Uri Dimant" <urid@.iscar.co.il>
wrote:
>Peter
>> Does index structure in SQL Server 2000 is different from that from SQL
>> Server 2005 ?
>No
Isn't there something about the uniquifiers for clustered indexes ...
But even if IIRC, that's not going to cost more than a percent or so
on a typical database. Is it?
J.|||JXStern
> Isn't there something about the uniquifiers for clustered indexes ...
No it is the same, i.e if you create CI but not UNIQUE , sql server adds
uniquifiers to the index
> But even if IIRC, that's not going to cost more than a percent or so
> on a typical database. Is it?
Sorry , what is IIRC?
"JXStern" <JXSternChangeX2R@.gte.net> wrote in message
news:vue8d351pro4etm0hr1bi04pp8802in7hj@.4ax.com...
> On Tue, 28 Aug 2007 14:20:06 +0300, "Uri Dimant" <urid@.iscar.co.il>
> wrote:
>>Peter
>> Does index structure in SQL Server 2000 is different from that from SQL
>> Server 2005 ?
>>No
> Isn't there something about the uniquifiers for clustered indexes ...
> But even if IIRC, that's not going to cost more than a percent or so
> on a typical database. Is it?
> J.
>|||On Wed, 29 Aug 2007 10:50:49 +0300, "Uri Dimant" <urid@.iscar.co.il>
wrote:
>JXStern
>> Isn't there something about the uniquifiers for clustered indexes ...
>No it is the same, i.e if you create CI but not UNIQUE , sql server adds
>uniquifiers to the index
>> But even if IIRC, that's not going to cost more than a percent or so
>> on a typical database. Is it?
>Sorry , what is IIRC?
If I Recall Correctly ... but it looks like I didn't.
J.
>"JXStern" <JXSternChangeX2R@.gte.net> wrote in message
>news:vue8d351pro4etm0hr1bi04pp8802in7hj@.4ax.com...
>> On Tue, 28 Aug 2007 14:20:06 +0300, "Uri Dimant" <urid@.iscar.co.il>
>> wrote:
>>Peter
>> Does index structure in SQL Server 2000 is different from that from SQL
>> Server 2005 ?
>>No
>> Isn't there something about the uniquifiers for clustered indexes ...
>> But even if IIRC, that's not going to cost more than a percent or so
>> on a typical database. Is it?
>> J.
>