Full Text Indexing Option Disabled

i can again/still/no longer manage full-text indexes on SQL Server.
i'm logged on locally to my server, as an administrator. EM is set to poll
the server.
Has anyone written a gui to manage SQL Server free-text indexing?
Hilary Cotter
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
"Ian Boyd" <admin@.SWIFTPA.NET> wrote in message
news:uG7DGLVXHHA.4520@.TK2MSFTNGP06.phx.gbl...
>i can again/still/no longer manage full-text indexes on SQL Server.
> i'm logged on locally to my server, as an administrator. EM is set to poll
> the server.
>
> Has anyone written a gui to manage SQL Server free-text indexing?
>
|||Have you tried this? It works for me every time.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlftzwiz.exe
Hilary Cotter
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
"Ian Boyd" <admin@.SWIFTPA.NET> wrote in message
news:uG7DGLVXHHA.4520@.TK2MSFTNGP06.phx.gbl...
>i can again/still/no longer manage full-text indexes on SQL Server.
> i'm logged on locally to my server, as an administrator. EM is set to poll
> the server.
>
> Has anyone written a gui to manage SQL Server free-text indexing?
>
|||> Have you tried this?>

> C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlftzwiz.exe
Do you know which tool is used to maintain a full-text catalog / enable
disable table / start stop automatic-change tracking / start top incremental
population / start stop full population / see what databases/tables/columns
are being FT indexed / view/edit the work breaker set on a column / etc?
|||Under the covers some procs are used in SQL 2000, in SQL 2005 its moved into
the engine.
In SQL 2000 in some of the earlier versions you could use some of the com
components to manage parts of it. Have a look at ssadmin.vbs in
C:\Program Files\Common Files\System\MSSearch\Bin
Hilary Cotter
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
"Ian Boyd" <ian.msnews010@.avatopia.com> wrote in message
news:ONMJiglYHHA.2320@.TK2MSFTNGP03.phx.gbl...
>
> Do you know which tool is used to maintain a full-text catalog / enable
> disable table / start stop automatic-change tracking / start top
> incremental population / start stop full population / see what
> databases/tables/columns are being FT indexed / view/edit the work breaker
> set on a column / etc?
>

Full tempdb log

Hi!
Does anybody know how SQL server behaves when below event is logged? Will it
stop or only part of its functionality will become unavailable?
Error: 9002, Severity: 17, State: 6 The log file for database 'tempdb' is
full. Back up the transaction log for the database to free up some log
space.
Regards
Silmar
Hi,
SQL Server service will not stop if Tempdb log is full. But all the
operations which require a tempdb (Sort, Group, joins) will fail
if tempdb log is full.
See the size of LDF file for Tempdb. If the size is too small then try to
increase the size or move it to a hard drive which have more space.
Thanks
Hari
SQL Server MVP
"Silmar" <silmar.NO_SPAM@.talex.pl> wrote in message
news:uRDob%23dZFHA.3852@.TK2MSFTNGP10.phx.gbl...
> Hi!
> Does anybody know how SQL server behaves when below event is logged? Will
> it stop or only part of its functionality will become unavailable?
> Error: 9002, Severity: 17, State: 6 The log file for database 'tempdb' is
> full. Back up the transaction log for the database to free up some log
> space.
> Regards
> Silmar
>

Full tempdb log

Hi!
Does anybody know how SQL server behaves when below event is logged? Will it
stop or only part of its functionality will become unavailable?
Error: 9002, Severity: 17, State: 6 The log file for database 'tempdb' is
full. Back up the transaction log for the database to free up some log
space.
Regards
SilmarHi,
SQL Server service will not stop if Tempdb log is full. But all the
operations which require a tempdb (Sort, Group, joins) will fail
if tempdb log is full.
See the size of LDF file for Tempdb. If the size is too small then try to
increase the size or move it to a hard drive which have more space.
Thanks
Hari
SQL Server MVP
"Silmar" <silmar.NO_SPAM@.talex.pl> wrote in message
news:uRDob%23dZFHA.3852@.TK2MSFTNGP10.phx.gbl...
> Hi!
> Does anybody know how SQL server behaves when below event is logged? Will
> it stop or only part of its functionality will become unavailable?
> Error: 9002, Severity: 17, State: 6 The log file for database 'tempdb' is
> full. Back up the transaction log for the database to free up some log
> space.
> Regards
> Silmar
>

Full tempdb log

Hi!
Does anybody know how SQL server behaves when below event is logged? Will it
stop or only part of its functionality will become unavailable?
Error: 9002, Severity: 17, State: 6 The log file for database 'tempdb' is
full. Back up the transaction log for the database to free up some log
space.
Regards
SilmarHi,
SQL Server service will not stop if Tempdb log is full. But all the
operations which require a tempdb (Sort, Group, joins) will fail
if tempdb log is full.
See the size of LDF file for Tempdb. If the size is too small then try to
increase the size or move it to a hard drive which have more space.
Thanks
Hari
SQL Server MVP
"Silmar" <silmar.NO_SPAM@.talex.pl> wrote in message
news:uRDob%23dZFHA.3852@.TK2MSFTNGP10.phx.gbl...
> Hi!
> Does anybody know how SQL server behaves when below event is logged? Will
> it stop or only part of its functionality will become unavailable?
> Error: 9002, Severity: 17, State: 6 The log file for database 'tempdb' is
> full. Back up the transaction log for the database to free up some log
> space.
> Regards
> Silmar
>

full backup and transaction log truncate

Hi,
I'm about how the backup system works in SQL Server. I'm using
the BULK LOGGED recovery model, I do regular full backups but my log
file is growing very large.
BOL says:
Full database backup, which backs up the entire database including the
transaction log
and it also says the BACKUP LOG truncates the log file, so I assumed
that BACKUP DATABASE would truncate the log file as well, but it doesn't
seem to be doing that. So the question is:
Does doing a full backup using BACKUP DATABASE truncate the log file?
Although I might be by the statement in BOL I actually hope
that BACKUP DATABASE does not truncate the log file, that way I can do
full backups whenever I want, for whatever reason and these backups will
not interfere with an automated full/differential/trans log backup system.
Thanks.BACKUP DATABASE does not truncate the inactive log portion. This means that
full backups do not interrupt a log backup sequence. If your most recent
backup is bad or incomplete, you can use an older backup as a starting point
and restore more logs to get back to the desired recovery point in time.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"John" <no@.spam> wrote in message
news:edF0K$deGHA.2068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I'm about how the backup system works in SQL Server. I'm using
> the BULK LOGGED recovery model, I do regular full backups but my log file
> is growing very large.
> BOL says:
> Full database backup, which backs up the entire database including the
> transaction log
> and it also says the BACKUP LOG truncates the log file, so I assumed that
> BACKUP DATABASE would truncate the log file as well, but it doesn't seem
> to be doing that. So the question is:
> Does doing a full backup using BACKUP DATABASE truncate the log file?
> Although I might be by the statement in BOL I actually hope that
> BACKUP DATABASE does not truncate the log file, that way I can do full
> backups whenever I want, for whatever reason and these backups will not
> interfere with an automated full/differential/trans log backup system.
> Thanks.|||John,
You have to backup the log in order to allow sql server to re-use the VLF
before the MinLSN. If these VLFs can not be reused and we reach the end of
the transaction log, then sql server will have to expand it.
Truncating the Transaction Log
http://msdn.microsoft.com/library/d...r />
_7vaf.asp
How to stop the transaction log of a SQL Server database from growing
unexpectedly
http://support.microsoft.com/?kbid=873235
AMB
"John" wrote:

> Hi,
> I'm about how the backup system works in SQL Server. I'm using
> the BULK LOGGED recovery model, I do regular full backups but my log
> file is growing very large.
> BOL says:
> Full database backup, which backs up the entire database including the
> transaction log
> and it also says the BACKUP LOG truncates the log file, so I assumed
> that BACKUP DATABASE would truncate the log file as well, but it doesn't
> seem to be doing that. So the question is:
> Does doing a full backup using BACKUP DATABASE truncate the log file?
> Although I might be by the statement in BOL I actually hope
> that BACKUP DATABASE does not truncate the log file, that way I can do
> full backups whenever I want, for whatever reason and these backups will
> not interfere with an automated full/differential/trans log backup system.
> Thanks.
>