Showing posts with label apart. Show all posts
Showing posts with label apart. Show all posts

Thursday, March 22, 2012

Database size

Hi all,
I need to estimate the disk space required for SQL Server
2000 and our application databases. Apart from the
table/index sizes (calculated as per logic given in BOL),
are there any other parameters to be considered to size
the disks ? Like more space for tempdb?
Is there any standard approach to estimate the disk space
required based on data growth?
Thanks,
HariHi Hari
Yes, the transaction log is a significant consideration. It is not possible
to accurately calculate size requirements for log space / growth as the log
storage format is not even published. Best bet with this is to make regular
observations, collect empirical data on growth rates between backup windows
& ensure you have enough space for log use / growth.
There's information on calculating database size in Books Online at:
http://msdn.microsoft.com/library/e...des_02_2h45.asp
The topic's also covered widely in books, including:
http://www.microsoft.com/mspress/bo...TableOfContents
HTH
Regards,
Greg Linwood
SQL Server MVP
"Hari" <anonymous@.discussions.microsoft.com> wrote in message
news:295d801c464af$6021d1a0$a301280a@.phx
.gbl...
> Hi all,
> I need to estimate the disk space required for SQL Server
> 2000 and our application databases. Apart from the
> table/index sizes (calculated as per logic given in BOL),
> are there any other parameters to be considered to size
> the disks ? Like more space for tempdb?
> Is there any standard approach to estimate the disk space
> required based on data growth?
> Thanks,
> Hari

Database size

Hi all,
I need to estimate the disk space required for SQL Server
2000 and our application databases. Apart from the
table/index sizes (calculated as per logic given in BOL),
are there any other parameters to be considered to size
the disks ? Like more space for tempdb?
Is there any standard approach to estimate the disk space
required based on data growth?
Thanks,
HariHi Hari
Yes, the transaction log is a significant consideration. It is not possible
to accurately calculate size requirements for log space / growth as the log
storage format is not even published. Best bet with this is to make regular
observations, collect empirical data on growth rates between backup windows
& ensure you have enough space for log use / growth.
There's information on calculating database size in Books Online at:
http://msdn.microsoft.com/library/en-us/createdb/cm_8_des_02_2h45.asp
The topic's also covered widely in books, including:
http://www.microsoft.com/mspress/books/toc/4944.asp#TableOfContents
HTH
Regards,
Greg Linwood
SQL Server MVP
"Hari" <anonymous@.discussions.microsoft.com> wrote in message
news:295d801c464af$6021d1a0$a301280a@.phx.gbl...
> Hi all,
> I need to estimate the disk space required for SQL Server
> 2000 and our application databases. Apart from the
> table/index sizes (calculated as per logic given in BOL),
> are there any other parameters to be considered to size
> the disks ? Like more space for tempdb?
> Is there any standard approach to estimate the disk space
> required based on data growth?
> Thanks,
> Hari

Wednesday, March 21, 2012

Database size

Hi all,
I need to estimate the disk space required for SQL Server
2000 and our application databases. Apart from the
table/index sizes (calculated as per logic given in BOL),
are there any other parameters to be considered to size
the disks ? Like more space for tempdb?
Is there any standard approach to estimate the disk space
required based on data growth?
Thanks,
Hari
Hi Hari
Yes, the transaction log is a significant consideration. It is not possible
to accurately calculate size requirements for log space / growth as the log
storage format is not even published. Best bet with this is to make regular
observations, collect empirical data on growth rates between backup windows
& ensure you have enough space for log use / growth.
There's information on calculating database size in Books Online at:
http://msdn.microsoft.com/library/en...es_02_2h45.asp
The topic's also covered widely in books, including:
http://www.microsoft.com/mspress/boo...ableOfContents
HTH
Regards,
Greg Linwood
SQL Server MVP
"Hari" <anonymous@.discussions.microsoft.com> wrote in message
news:295d801c464af$6021d1a0$a301280a@.phx.gbl...
> Hi all,
> I need to estimate the disk space required for SQL Server
> 2000 and our application databases. Apart from the
> table/index sizes (calculated as per logic given in BOL),
> are there any other parameters to be considered to size
> the disks ? Like more space for tempdb?
> Is there any standard approach to estimate the disk space
> required based on data growth?
> Thanks,
> Hari

Friday, February 24, 2012

Database Recovery Problem

Greetings,
I am attempting to restore some databases to a SQL Server
2000 Installation that fell apart after loading SP4 for
Windows 2000. The backups were made using Veritas Backup
Exec 8.6. on a remote backup server. When I do a restore
on my databases Veritas restores all of them to the the
SQL Server and they appear in Enterprise Manager. However
the databases are in a state of loading and I cannot seem
to find a way to take them out of this loading state to
complete the restore to normal operation.
I am new to SQL Server so I am at a loss as to what to do
to rectify this situation.
Thanks in advance for the help.
Joe.If you have restored the databases with norecovery you can
restore database mydb with recovery
to bring it on-line.
If in fact veritas hasn't completed the restore then you
will have to go back to that product.
>"Joe Toth" <jtoth@.cmefcu.org> wrote in message
>news:029d01c34727$da60cee0$a401280a@.phx.gbl...
>> Greetings,
>> I am attempting to restore some databases to a SQL
Server
>> 2000 Installation that fell apart after loading SP4 for
>> Windows 2000. The backups were made using Veritas Backup
>> Exec 8.6. on a remote backup server. When I do a restore
>> on my databases Veritas restores all of them to the the
>> SQL Server and they appear in Enterprise Manager.
However
>> the databases are in a state of loading and I cannot
seem
>> to find a way to take them out of this loading state to
>> complete the restore to normal operation.
>> I am new to SQL Server so I am at a loss as to what to
do
>> to rectify this situation.
>> Thanks in advance for the help.
>> Joe.
>
>.
>|||It's been a few months since I restored from BE, but I
think it's an option when configuring the restore on the
SQL tab. The db is left in this state so you can apply
logs if you need to.
--Scott
>--Original Message--
>Greetings,
>I am attempting to restore some databases to a SQL Server
>2000 Installation that fell apart after loading SP4 for
>Windows 2000. The backups were made using Veritas Backup
>Exec 8.6. on a remote backup server. When I do a restore
>on my databases Veritas restores all of them to the the
>SQL Server and they appear in Enterprise Manager. However
>the databases are in a state of loading and I cannot seem
>to find a way to take them out of this loading state to
>complete the restore to normal operation.
>I am new to SQL Server so I am at a loss as to what to do
>to rectify this situation.
>Thanks in advance for the help.
>Joe.
>.
>