Hi,
Here's the backup script,
BACKUP DATABASE [PRODPFR] TO DISK = N'F:\MSSQLBackup\ProdPfr_Bkp' WITH
NOINIT , NOUNLOAD , NAME = N'PRODPFR backup', NOSKIP , STATS = 10,
DESCRIPTION = N'SQL Production Backup', NOFORMAT DECLARE @i INT
select @i = position from msdb..backupset where
database_name='PRODPFR'and type!='F' and backup_set_id=(select
max(backup_set_id) from msdb..backupset where database_name='PRODPFR')
RESTORE VERIFYONLY FROM DISK = N'F:\MSSQLBackup\ProdPfr_Bkp' WITH
FILE = @i
Please advise what is wrong.
How do i check if there are full-text catalogs hanging.
Thanks.
[quoted text, click to view] Hilary Cotter wrote:
> Can we see your backup statement? Also are there full-text catalogs hanging
> off this database?
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
>
http://www.nwsu.com/0974973602.html >
> Looking for a FAQ on Indexing Services/SQL FTS
>
http://www.indexserverfaq.com >
>
>
> <aaileng@yahoo.com> wrote in message
> news:1161222153.514252.225380@b28g2000cwb.googlegroups.com...
> > Hi,
> >
> > We have an database which is about the file size of 730MB, this db is
> > set configure with publisher and will always push data to our backup
> > server database. When we backup this db, the database backup filesize
> > is actually 85GB (full backup from SQL).
> > Anyone has any idea why is my database backup filesize so big. Is
> > there any settings we have configure wrongly?
> > As we are going to populate more customer data into this database,
> > expected to increase the databse filesize to 2.5GB, will the backup
> > filesize be triple? If this is the case, we will need to buy
> > additional harddisk to cater for this.
> >
> > Thanks!!
> >
