RESTORE FILELISTONLY
FROM DISK = 'C:\Full0100.BAK'
Here is the result
database d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\database
..mdf
database _Log d:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\database _log.ldf
sysft_PhraseologyIndex d:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\FTData\PhraseologyIndex
I would like to remove the sysft_PhraseologyIndex. The database server does
not have full-text component installed (this particular database was created
with sql server 2000 that supported the full-text indexing and upgraded to
sql server 2005 that does not support full-text index)
Thanks
You need to disable full-text indexing and then remove the
sysft_phraseologyindex file.
"iiman" <nospam@.nospam.com> wrote in message
news:evP$tdahHHA.1220@.TK2MSFTNGP03.phx.gbl...
> RESTORE FILELISTONLY
> FROM DISK = 'C:\Full0100.BAK'
> Here is the result
> database d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\database
> .mdf
> database _Log d:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\database _log.ldf
> sysft_PhraseologyIndex d:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\FTData\PhraseologyIndex
> I would like to remove the sysft_PhraseologyIndex. The database server
> does
> not have full-text component installed (this particular database was
> created
> with sql server 2000 that supported the full-text indexing and upgraded to
> sql server 2005 that does not support full-text index)
> Thanks
>
>
|||I tried,
ALTER DATABASE scope
REMOVE FILE sysft_PhraseologyIndex
I get
Msg 5020, Level 16, State 1, Line 1
The primary data or log file cannot be removed from a database.
How do I remove the file?
Thanks
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e$8GzmhhHHA.4596@.TK2MSFTNGP05.phx.gbl...
> You need to disable full-text indexing and then remove the
> sysft_phraseologyindex file.
> "iiman" <nospam@.nospam.com> wrote in message
> news:evP$tdahHHA.1220@.TK2MSFTNGP03.phx.gbl...
>
2012年3月11日星期日
2012年2月24日星期五
FULL and Tran Backup
The .bak and .trn seem to eat up too much disk space. What are the best
practices? We have to have point -in- time capability so it needs to be in
Full recovery mode. How do you prevent this from crashing the server? Do i
have to buy more disk. Appreciate any advice...> The .bak and .trn seem to eat up too much disk space. What are the best
> practices?
Delete the old backup files, determined by the number of backup generations you want to have on
disk. If you don't use the maint wizard, make sure that you do overwrite at suitable schedule (see
the INIT and NOINIT options to the backup command).
And, needless to say, make sure you also copy the backup files to other machine, tape and/or
offsite.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"morphius" <morphius@.discussions.microsoft.com> wrote in message
news:EFD903D5-3AD8-44E2-B7AC-815BD14DBC94@.microsoft.com...
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...|||Hi
You don't say how long you keep the backups on disc and when it would be
acceptable to delete them. If they are stored safely elsewhere you can delete
the files but this will be at the expense of increased time needed to
recover. You will need to decide what the cut off is for this and if you
don't have enough disc space to hold that many backups, then you will need to
get more.
HTH
John
"morphius" wrote:
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...
practices? We have to have point -in- time capability so it needs to be in
Full recovery mode. How do you prevent this from crashing the server? Do i
have to buy more disk. Appreciate any advice...> The .bak and .trn seem to eat up too much disk space. What are the best
> practices?
Delete the old backup files, determined by the number of backup generations you want to have on
disk. If you don't use the maint wizard, make sure that you do overwrite at suitable schedule (see
the INIT and NOINIT options to the backup command).
And, needless to say, make sure you also copy the backup files to other machine, tape and/or
offsite.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"morphius" <morphius@.discussions.microsoft.com> wrote in message
news:EFD903D5-3AD8-44E2-B7AC-815BD14DBC94@.microsoft.com...
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...|||Hi
You don't say how long you keep the backups on disc and when it would be
acceptable to delete them. If they are stored safely elsewhere you can delete
the files but this will be at the expense of increased time needed to
recover. You will need to decide what the cut off is for this and if you
don't have enough disc space to hold that many backups, then you will need to
get more.
HTH
John
"morphius" wrote:
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...
FULL and Tran Backup
The .bak and .trn seem to eat up too much disk space. What are the best
practices? We have to have point -in- time capability so it needs to be in
Full recovery mode. How do you prevent this from crashing the server? Do i
have to buy more disk. Appreciate any advice...> The .bak and .trn seem to eat up too much disk space. What are the best
> practices?
Delete the old backup files, determined by the number of backup generations
you want to have on
disk. If you don't use the maint wizard, make sure that you do overwrite at
suitable schedule (see
the INIT and NOINIT options to the backup command).
And, needless to say, make sure you also copy the backup files to other mach
ine, tape and/or
offsite.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"morphius" <morphius@.discussions.microsoft.com> wrote in message
news:EFD903D5-3AD8-44E2-B7AC-815BD14DBC94@.microsoft.com...
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...|||Hi
You don't say how long you keep the backups on disc and when it would be
acceptable to delete them. If they are stored safely elsewhere you can delet
e
the files but this will be at the expense of increased time needed to
recover. You will need to decide what the cut off is for this and if you
don't have enough disc space to hold that many backups, then you will need t
o
get more.
HTH
John
"morphius" wrote:
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...
practices? We have to have point -in- time capability so it needs to be in
Full recovery mode. How do you prevent this from crashing the server? Do i
have to buy more disk. Appreciate any advice...> The .bak and .trn seem to eat up too much disk space. What are the best
> practices?
Delete the old backup files, determined by the number of backup generations
you want to have on
disk. If you don't use the maint wizard, make sure that you do overwrite at
suitable schedule (see
the INIT and NOINIT options to the backup command).
And, needless to say, make sure you also copy the backup files to other mach
ine, tape and/or
offsite.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"morphius" <morphius@.discussions.microsoft.com> wrote in message
news:EFD903D5-3AD8-44E2-B7AC-815BD14DBC94@.microsoft.com...
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...|||Hi
You don't say how long you keep the backups on disc and when it would be
acceptable to delete them. If they are stored safely elsewhere you can delet
e
the files but this will be at the expense of increased time needed to
recover. You will need to decide what the cut off is for this and if you
don't have enough disc space to hold that many backups, then you will need t
o
get more.
HTH
John
"morphius" wrote:
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...
FULL and Tran Backup
The .bak and .trn seem to eat up too much disk space. What are the best
practices? We have to have point -in- time capability so it needs to be in
Full recovery mode. How do you prevent this from crashing the server? Do i
have to buy more disk. Appreciate any advice...
Hi
You don't say how long you keep the backups on disc and when it would be
acceptable to delete them. If they are stored safely elsewhere you can delete
the files but this will be at the expense of increased time needed to
recover. You will need to decide what the cut off is for this and if you
don't have enough disc space to hold that many backups, then you will need to
get more.
HTH
John
"morphius" wrote:
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...
practices? We have to have point -in- time capability so it needs to be in
Full recovery mode. How do you prevent this from crashing the server? Do i
have to buy more disk. Appreciate any advice...
Hi
You don't say how long you keep the backups on disc and when it would be
acceptable to delete them. If they are stored safely elsewhere you can delete
the files but this will be at the expense of increased time needed to
recover. You will need to decide what the cut off is for this and if you
don't have enough disc space to hold that many backups, then you will need to
get more.
HTH
John
"morphius" wrote:
> The .bak and .trn seem to eat up too much disk space. What are the best
> practices? We have to have point -in- time capability so it needs to be in
> Full recovery mode. How do you prevent this from crashing the server? Do i
> have to buy more disk. Appreciate any advice...
订阅：
博文 (Atom)