I got 2 questions, if tempdb is full, how to fix it? 2. if I have full backup
yesterday and no transaction log today and I delete data by accident, is
there any way to recover it?
Thanks.1)
http://www.aspfaq.com/show.asp?id=2446
2)
http://www.lumigent.com/ --explorer log for sql
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:A292519F-B554-4193-9437-9B74EAE07151@.microsoft.com...
>I got 2 questions, if tempdb is full, how to fix it? 2. if I have full
>backup
> yesterday and no transaction log today and I delete data by accident, is
> there any way to recover it?
> Thanks.
>
Showing posts with label delete. Show all posts
Showing posts with label delete. Show all posts
Friday, March 30, 2012
I got 2 question, if tempdb is full, how to fix it? 2. if I have f
I got 2 questions, if tempdb is full, how to fix it? 2. if I have full backu
p
yesterday and no transaction log today and I delete data by accident, is
there any way to recover it?
Thanks.1)
http://www.aspfaq.com/show.asp?id=2446
2)
http://www.lumigent.com/ --explorer log for sql
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:A292519F-B554-4193-9437-9B74EAE07151@.microsoft.com...
>I got 2 questions, if tempdb is full, how to fix it? 2. if I have full
>backup
> yesterday and no transaction log today and I delete data by accident, is
> there any way to recover it?
> Thanks.
>
p
yesterday and no transaction log today and I delete data by accident, is
there any way to recover it?
Thanks.1)
http://www.aspfaq.com/show.asp?id=2446
2)
http://www.lumigent.com/ --explorer log for sql
"Iter" <Iter@.discussions.microsoft.com> wrote in message
news:A292519F-B554-4193-9437-9B74EAE07151@.microsoft.com...
>I got 2 questions, if tempdb is full, how to fix it? 2. if I have full
>backup
> yesterday and no transaction log today and I delete data by accident, is
> there any way to recover it?
> Thanks.
>
Monday, March 26, 2012
I can't work out. Duplicate row
Dear all,
I am not be able to delete a row in the following table:
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[tblSysRights]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[tblSysRights]
GO
CREATE TABLE [dbo].[tblSysRights] (
[sinRightID] [smallint] IDENTITY (1, 1) NOT NULL ,
[sinUserID] [smallint] NOT NULL ,
[sinApplicationID] [smallint] NOT NULL ,
[sinType] [smallint] NULL
) ON [PRIMARY]
GO
No indexes. No constraints. No relationships. What on earth hell is happenin
g?
SELECT *
FROM tblSysRights
WHERE (sinUserID = 61) AND (sinApplicationID = 163)
725 61 163 null
725 61 163 null
I obtain a warning which tell me:
"key column information is insufficient. too many rows affected"
Thanks in advance and best regards,Set RowCount 1
Delete
FROM tblSysRights
WHERE (sinUserID = 61) AND (sinApplicationID = 163)
Set RowCount 0
Madhivanan|||Enric,
> I am not be able to delete a row in the following table:
Can you be more specific?
From where and how are you trying delete the row?
AMB
"Enric" wrote:
> Dear all,
> I am not be able to delete a row in the following table:
> if exists (select * from dbo.sysobjects where id =
> object_id(N'[dbo].[tblSysRights]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
> drop table [dbo].[tblSysRights]
> GO
> CREATE TABLE [dbo].[tblSysRights] (
> [sinRightID] [smallint] IDENTITY (1, 1) NOT NULL ,
> [sinUserID] [smallint] NOT NULL ,
> [sinApplicationID] [smallint] NOT NULL ,
> [sinType] [smallint] NULL
> ) ON [PRIMARY]
> GO
> No indexes. No constraints. No relationships. What on earth hell is happen
ing?
> SELECT *
> FROM tblSysRights
> WHERE (sinUserID = 61) AND (sinApplicationID = 163)
> 725 61 163 null
> 725 61 163 null
> I obtain a warning which tell me:
> "key column information is insufficient. too many rows affected"
> Thanks in advance and best regards,
>
>|||Thanks for that Madhinavan.
Done successfully.
Thanks Alejandro, too.
Regards,
"Alejandro Mesa" wrote:
> Enric,
>
> Can you be more specific?
> From where and how are you trying delete the row?
>
> AMB
>
> "Enric" wrote:
>|||Just to add a couple of points. For elimination of duplicates, refer to:
http://support.microsoft.com/defaul...b;EN-US;q139444
Use keys in all your tables, and you will avoid a lot of such headaches. On
a related note, a couple of comments:
* You seem to have an identity column which is constrained to be unique, but
apparently it seems to be violated with SET IDENTITY_INSERT ON setting.
Check where the "hole" is.
* Your naming conventions are stale which can be better -- search for some
good guidelines in the archives of this newsgroup.
* Use Query Analyzer for testing your queries, the EM query interface is
buggy and has certain limitations.
* And most importantly, use primary keys in your tables. In relational
database, a value is identified using <table, column, key> triplet. With
duplicates, such identification becomes impossible and relational operations
cannot be used beneficially. The impossibility of logically deleting one row
out of duplicates is often cited as a prime illustration of the consequence
of allowing duplicates by SQL. ( SQL language inventors and its flag bearers
should take the credit, for even standardizing them ! )
Anith|||Thanks for that Anith.
That table was defined without identity fields or key. Just a mess-up.
Best Regards,
"Anith Sen" wrote:
> Just to add a couple of points. For elimination of duplicates, refer to:
> http://support.microsoft.com/defaul...b;EN-US;q139444
> Use keys in all your tables, and you will avoid a lot of such headaches. O
n
> a related note, a couple of comments:
> * You seem to have an identity column which is constrained to be unique, b
ut
> apparently it seems to be violated with SET IDENTITY_INSERT ON setting.
> Check where the "hole" is.
> * Your naming conventions are stale which can be better -- search for some
> good guidelines in the archives of this newsgroup.
> * Use Query Analyzer for testing your queries, the EM query interface is
> buggy and has certain limitations.
> * And most importantly, use primary keys in your tables. In relational
> database, a value is identified using <table, column, key> triplet. With
> duplicates, such identification becomes impossible and relational operatio
ns
> cannot be used beneficially. The impossibility of logically deleting one r
ow
> out of duplicates is often cited as a prime illustration of the consequenc
e
> of allowing duplicates by SQL. ( SQL language inventors and its flag beare
rs
> should take the credit, for even standardizing them ! )
> --
> Anith
>
>
I am not be able to delete a row in the following table:
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[tblSysRights]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[tblSysRights]
GO
CREATE TABLE [dbo].[tblSysRights] (
[sinRightID] [smallint] IDENTITY (1, 1) NOT NULL ,
[sinUserID] [smallint] NOT NULL ,
[sinApplicationID] [smallint] NOT NULL ,
[sinType] [smallint] NULL
) ON [PRIMARY]
GO
No indexes. No constraints. No relationships. What on earth hell is happenin
g?
SELECT *
FROM tblSysRights
WHERE (sinUserID = 61) AND (sinApplicationID = 163)
725 61 163 null
725 61 163 null
I obtain a warning which tell me:
"key column information is insufficient. too many rows affected"
Thanks in advance and best regards,Set RowCount 1
Delete
FROM tblSysRights
WHERE (sinUserID = 61) AND (sinApplicationID = 163)
Set RowCount 0
Madhivanan|||Enric,
> I am not be able to delete a row in the following table:
Can you be more specific?
From where and how are you trying delete the row?
AMB
"Enric" wrote:
> Dear all,
> I am not be able to delete a row in the following table:
> if exists (select * from dbo.sysobjects where id =
> object_id(N'[dbo].[tblSysRights]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
> drop table [dbo].[tblSysRights]
> GO
> CREATE TABLE [dbo].[tblSysRights] (
> [sinRightID] [smallint] IDENTITY (1, 1) NOT NULL ,
> [sinUserID] [smallint] NOT NULL ,
> [sinApplicationID] [smallint] NOT NULL ,
> [sinType] [smallint] NULL
> ) ON [PRIMARY]
> GO
> No indexes. No constraints. No relationships. What on earth hell is happen
ing?
> SELECT *
> FROM tblSysRights
> WHERE (sinUserID = 61) AND (sinApplicationID = 163)
> 725 61 163 null
> 725 61 163 null
> I obtain a warning which tell me:
> "key column information is insufficient. too many rows affected"
> Thanks in advance and best regards,
>
>|||Thanks for that Madhinavan.
Done successfully.
Thanks Alejandro, too.
Regards,
"Alejandro Mesa" wrote:
> Enric,
>
> Can you be more specific?
> From where and how are you trying delete the row?
>
> AMB
>
> "Enric" wrote:
>|||Just to add a couple of points. For elimination of duplicates, refer to:
http://support.microsoft.com/defaul...b;EN-US;q139444
Use keys in all your tables, and you will avoid a lot of such headaches. On
a related note, a couple of comments:
* You seem to have an identity column which is constrained to be unique, but
apparently it seems to be violated with SET IDENTITY_INSERT ON setting.
Check where the "hole" is.
* Your naming conventions are stale which can be better -- search for some
good guidelines in the archives of this newsgroup.
* Use Query Analyzer for testing your queries, the EM query interface is
buggy and has certain limitations.
* And most importantly, use primary keys in your tables. In relational
database, a value is identified using <table, column, key> triplet. With
duplicates, such identification becomes impossible and relational operations
cannot be used beneficially. The impossibility of logically deleting one row
out of duplicates is often cited as a prime illustration of the consequence
of allowing duplicates by SQL. ( SQL language inventors and its flag bearers
should take the credit, for even standardizing them ! )
Anith|||Thanks for that Anith.
That table was defined without identity fields or key. Just a mess-up.
Best Regards,
"Anith Sen" wrote:
> Just to add a couple of points. For elimination of duplicates, refer to:
> http://support.microsoft.com/defaul...b;EN-US;q139444
> Use keys in all your tables, and you will avoid a lot of such headaches. O
n
> a related note, a couple of comments:
> * You seem to have an identity column which is constrained to be unique, b
ut
> apparently it seems to be violated with SET IDENTITY_INSERT ON setting.
> Check where the "hole" is.
> * Your naming conventions are stale which can be better -- search for some
> good guidelines in the archives of this newsgroup.
> * Use Query Analyzer for testing your queries, the EM query interface is
> buggy and has certain limitations.
> * And most importantly, use primary keys in your tables. In relational
> database, a value is identified using <table, column, key> triplet. With
> duplicates, such identification becomes impossible and relational operatio
ns
> cannot be used beneficially. The impossibility of logically deleting one r
ow
> out of duplicates is often cited as a prime illustration of the consequenc
e
> of allowing duplicates by SQL. ( SQL language inventors and its flag beare
rs
> should take the credit, for even standardizing them ! )
> --
> Anith
>
>
Friday, March 23, 2012
I cant delete records
Hi,
My DB is MS SQL Server. I wrote a SQL statement to remove rows from a table as following.
DELETE FROM #TableA
FROM #TableA AS t1
LEFT JOIN #TableA AS t2 ON (t1.Index - 1) = t2.Index
WHERE t2.Index IS NULL
========================================
When I tried to execute it, I got the following error message.
Error Message: The table '#TableA' is ambiguous.
Thanks for your help.Interesting problem, never thought about it. I can imagine that MSSQL has some problem with guessing what to do.
I know it is not an answer to your question, the following syntax should do the same (if I got the query right) :
DELETE FROM #TableA
WHERE Index-1 NOT IN (SELECT Index FROM #TableA)
ps. Do you really have columns named "Index"|||You have answered my question.
Many Thanks.
I don't have a column named "Index", it is a alias to simply my question.
My DB is MS SQL Server. I wrote a SQL statement to remove rows from a table as following.
DELETE FROM #TableA
FROM #TableA AS t1
LEFT JOIN #TableA AS t2 ON (t1.Index - 1) = t2.Index
WHERE t2.Index IS NULL
========================================
When I tried to execute it, I got the following error message.
Error Message: The table '#TableA' is ambiguous.
Thanks for your help.Interesting problem, never thought about it. I can imagine that MSSQL has some problem with guessing what to do.
I know it is not an answer to your question, the following syntax should do the same (if I got the query right) :
DELETE FROM #TableA
WHERE Index-1 NOT IN (SELECT Index FROM #TableA)
ps. Do you really have columns named "Index"|||You have answered my question.
Many Thanks.
I don't have a column named "Index", it is a alias to simply my question.
i cant delete a row
i cant delete a row on my table. when i click delete it say : "Insufficient key column information for updating or refreshing....." what can i do?The message smells like you might be using Microsoft Access to edit a table stored in Microsoft SQL, but that you don't have all of the defined key columns in the edit control. If that is correct:
1. Verify that there is a defined key
1a. Should be a PRIMARY KEY definition
1b. Could be a UNIQUE constraint
1c. Might be a UNIQUE INDEX
2. Identify all columns in all of the potential defined key(s) from step 1.
3. Ensure that all of the columns from at least one of the defined keys are present in your edit control.
-PatP|||thanks but i didnt use access. i copy and paste a row in my table. then i wanted to delete that row but i cant delete. all of my other rows can be cleaned but that row cant be delete.|||Nope, it isn't possible to "copy and paste a row in my table" because there isn't any GUI representation for a table. What you are doing (very possibly without realizing it) is copying and pasting within some application running on your machine, not actually on the table itself.
Since you haven't given us (the readers) many clues, but you have ruled out Microsoft Access, I'll make another guess... This time I'll guess Captain Peacock, in the Drawing Room... Oh wait, wrong game! ;)
Let's try this guess: Are you possibly using SQL Enterprise Manager, and Editing a table grid control? If so, please let me know and we can start to solve your problem... If not, I might try to guess again!
Just in case you didn't get the idea, I'm frustrated. You're asking me to help you solve a problem, but you haven't given me anything concrete to work from. I assume that you are using SQL Server, and that you haven't used it very much so you're handicapped in explaining your problem, and it appears that English isn't your native language which would further complicate things for you... I'm trying to help, but I need you to help me more so that I can help you!
If you can read English comfortably, please see this forum's FAQ for Brett Kaiser's excellent suggestions for How to Ask a Question to Get Quick and Correct Answers (http://www.dbforums.com/showthread.php?t=1212452#post4527530).
-PatP|||yes! you are right. im sorry. now i am using sql server 2000 enterprise manager. i create a table (same nortwind "order details"). remember i create an olap cube such as nwind
here is my fields:
accountno (varchar50)
medicineno(nvarchar15)
saleprice(float8)
quantity(float8)
i click return all rows and enter my records
1 101 $4 3
1 102 $3 2
2 102 $5 3
3 207 $2 1
....................
56 101 $4 2
and then i copy this row (2 102 $3 2) and paste it
........................
56 101 $4 2
2 102 $3 2
then i wanted to delete that row (2 102 $3 2)
but it cant be deleted. warning: "key column info insufficient or wrong. updating affects more rows" (i translated english. maybe it can be wrong)|||Have dealt with this in the past dealing with others issues.
You need to write a delete statment to accomplish this in query analyzer.
delete from table where accountno = 2
try inserting a new row as follows|||The problem stems from the fact that you do not have a unique primary key defined on your table. Thus, when you try to delete one record SQL Server cannot tell which record it is.
Add a primary key to your table. A surrogate key will do fine. But I also agree that you should not edit data from the Enterprise Manager GUI. Use Query Analyzer.|||thanks i will try
1. Verify that there is a defined key
1a. Should be a PRIMARY KEY definition
1b. Could be a UNIQUE constraint
1c. Might be a UNIQUE INDEX
2. Identify all columns in all of the potential defined key(s) from step 1.
3. Ensure that all of the columns from at least one of the defined keys are present in your edit control.
-PatP|||thanks but i didnt use access. i copy and paste a row in my table. then i wanted to delete that row but i cant delete. all of my other rows can be cleaned but that row cant be delete.|||Nope, it isn't possible to "copy and paste a row in my table" because there isn't any GUI representation for a table. What you are doing (very possibly without realizing it) is copying and pasting within some application running on your machine, not actually on the table itself.
Since you haven't given us (the readers) many clues, but you have ruled out Microsoft Access, I'll make another guess... This time I'll guess Captain Peacock, in the Drawing Room... Oh wait, wrong game! ;)
Let's try this guess: Are you possibly using SQL Enterprise Manager, and Editing a table grid control? If so, please let me know and we can start to solve your problem... If not, I might try to guess again!
Just in case you didn't get the idea, I'm frustrated. You're asking me to help you solve a problem, but you haven't given me anything concrete to work from. I assume that you are using SQL Server, and that you haven't used it very much so you're handicapped in explaining your problem, and it appears that English isn't your native language which would further complicate things for you... I'm trying to help, but I need you to help me more so that I can help you!
If you can read English comfortably, please see this forum's FAQ for Brett Kaiser's excellent suggestions for How to Ask a Question to Get Quick and Correct Answers (http://www.dbforums.com/showthread.php?t=1212452#post4527530).
-PatP|||yes! you are right. im sorry. now i am using sql server 2000 enterprise manager. i create a table (same nortwind "order details"). remember i create an olap cube such as nwind
here is my fields:
accountno (varchar50)
medicineno(nvarchar15)
saleprice(float8)
quantity(float8)
i click return all rows and enter my records
1 101 $4 3
1 102 $3 2
2 102 $5 3
3 207 $2 1
....................
56 101 $4 2
and then i copy this row (2 102 $3 2) and paste it
........................
56 101 $4 2
2 102 $3 2
then i wanted to delete that row (2 102 $3 2)
but it cant be deleted. warning: "key column info insufficient or wrong. updating affects more rows" (i translated english. maybe it can be wrong)|||Have dealt with this in the past dealing with others issues.
You need to write a delete statment to accomplish this in query analyzer.
delete from table where accountno = 2
try inserting a new row as follows|||The problem stems from the fact that you do not have a unique primary key defined on your table. Thus, when you try to delete one record SQL Server cannot tell which record it is.
Add a primary key to your table. A surrogate key will do fine. But I also agree that you should not edit data from the Enterprise Manager GUI. Use Query Analyzer.|||thanks i will try
Monday, March 19, 2012
I cannot delete, remove, rebuild, or repopulate fulltext catalogue.
I have SQL Server 7 on an NT server. The catalogue has
been working for a long time, however, it stopped and I
cannot seem to get it to repopulate. It stopped during an
incremental population. I have tried deleting it so I can
rebuild it, but whatever I try to do, I get the same
message: "Database is not full-text enabled yet". Can
anyone help?
Linda,
Could you review your server's Application Event log for any "Microsoft
Search" or MssCi source events (warnings, or errors) near the day & time
that the FT Catalog stopped working? Additionally, review the server System
Event log for any relate disk i/o warnings of low free disk space on both
your server's system disk drive (usually, the C:\ drive) or the drive where
the FT Catalog reside.
Most likely the FT Catalog is corrupt (and you may see a MssCi event with a
stack trace in it) and you may be in a "Catch-22" situation where you cannot
drop the FT Catalog (please try this), nor re-build it as well as not able
to run a Full or Incremental Population. IF so and depending upon the errors
in the Application event log, I have as sql script that you can "manually
de-reference" the FT Catalog, however, it is highly dependent on the type of
errors you are seeing and you may need to remove and re-install the FTS and
MSSearch components as well. Please, post any related application event
errors in your reply!
Thanks,
John
"Linda" <anonymous@.discussions.microsoft.com> wrote in message
news:2865701c46458$a8cf3cf0$a501280a@.phx.gbl...
> I have SQL Server 7 on an NT server. The catalogue has
> been working for a long time, however, it stopped and I
> cannot seem to get it to repopulate. It stopped during an
> incremental population. I have tried deleting it so I can
> rebuild it, but whatever I try to do, I get the same
> message: "Database is not full-text enabled yet". Can
> anyone help?
|||John,
I examined all logs but could not find anything concerning
the FT catalog. The logs for that date are no longer
available. It seems that the server was rebooted while
the catalog was performing an incremental update, freezing
the catalog.
I tried to drop it, but again got the message "Database is
not full-text enabled Please run
sp_fulltext_database 'enable' . When I do that, the query
never finishes. I have to reboot the server to clear it.
Maybe the script can help?
Thanks!!
Linda
>--Original Message--
>Linda,
>Could you review your server's Application Event log for
any "Microsoft
>Search" or MssCi source events (warnings, or errors) near
the day & time
>that the FT Catalog stopped working? Additionally, review
the server System
>Event log for any relate disk i/o warnings of low free
disk space on both
>your server's system disk drive (usually, the C:\ drive)
or the drive where
>the FT Catalog reside.
>Most likely the FT Catalog is corrupt (and you may see a
MssCi event with a
>stack trace in it) and you may be in a "Catch-22"
situation where you cannot
>drop the FT Catalog (please try this), nor re-build it as
well as not able
>to run a Full or Incremental Population. IF so and
depending upon the errors
>in the Application event log, I have as sql script that
you can "manually
>de-reference" the FT Catalog, however, it is highly
dependent on the type of
>errors you are seeing and you may need to remove and re-
install the FTS and
>MSSearch components as well. Please, post any related
application event
>errors in your reply!
>Thanks,
>John
>
>"Linda" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:2865701c46458$a8cf3cf0$a501280a@.phx.gbl...
an[vbcol=seagreen]
can
>
>.
>
|||Linda,
I emailed you the SQL Server 7.0 version to "manually de-reference" a FT
Catalog, please use it with caution as it requires modification to both
system tables as well as the registry hive. I highly recommend that you
backup both your database as well as the registry hive BEFORE using the
script as well as testing the procedure in a test environment prior to using
it.
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...[vbcol=seagreen]
> John,
> I examined all logs but could not find anything concerning
> the FT catalog. The logs for that date are no longer
> available. It seems that the server was rebooted while
> the catalog was performing an incremental update, freezing
> the catalog.
> I tried to drop it, but again got the message "Database is
> not full-text enabled Please run
> sp_fulltext_database 'enable' . When I do that, the query
> never finishes. I have to reboot the server to clear it.
> Maybe the script can help?
> Thanks!!
> Linda
> any "Microsoft
> the day & time
> the server System
> disk space on both
> or the drive where
> MssCi event with a
> situation where you cannot
> well as not able
> depending upon the errors
> you can "manually
> dependent on the type of
> install the FTS and
> application event
> message
> an
> can
|||John,
Before I received your SQL I tried something that worked.
Since I couldn't stop the MSSearch engine, I changed the
startup from automatic to manual. Then I rebooted the
server. With MSSearch service off, I was then able to
manipulate the gatherlogs so I copied the entire folders
to another directory (as a backup). Then I deleted the
original folders, started the service, and
ran "sp_fulltext_database 'enable'" which worked this
time. I was then able to rebuild the fulltext catalogue
and repopulate it. The search is working fine now. You
were right...I think the files were corrupted. We are
still trying to find out how that happened.
Thanks for your help. I will keep the SQL in case that
happens again.
Linda
>--Original Message--
>Linda,
>I emailed you the SQL Server 7.0 version to "manually de-
reference" a FT
>Catalog, please use it with caution as it requires
modification to both
>system tables as well as the registry hive. I highly
recommend that you
>backup both your database as well as the registry hive
BEFORE using the
>script as well as testing the procedure in a test
environment prior to using[vbcol=seagreen]
>it.
>Regards,
>John
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...
concerning[vbcol=seagreen]
freezing[vbcol=seagreen]
is[vbcol=seagreen]
query[vbcol=seagreen]
it.[vbcol=seagreen]
for[vbcol=seagreen]
near[vbcol=seagreen]
review[vbcol=seagreen]
drive)[vbcol=seagreen]
a[vbcol=seagreen]
as[vbcol=seagreen]
re-[vbcol=seagreen]
has[vbcol=seagreen]
and I[vbcol=seagreen]
during[vbcol=seagreen]
I
>
>.
>
|||You're welcome, Linda,
As they say, there are many ways to 'skin a cat' (not that i'm anti-cat ;-),
but there are many ways to solve a problem and to further mix my metaphors,
the proof is in the pudding, i.e., whatever works, go with it!
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:2d96a01c46a6d$2d545ea0$a501280a@.phx.gbl...[vbcol=seagreen]
> John,
> Before I received your SQL I tried something that worked.
> Since I couldn't stop the MSSearch engine, I changed the
> startup from automatic to manual. Then I rebooted the
> server. With MSSearch service off, I was then able to
> manipulate the gatherlogs so I copied the entire folders
> to another directory (as a backup). Then I deleted the
> original folders, started the service, and
> ran "sp_fulltext_database 'enable'" which worked this
> time. I was then able to rebuild the fulltext catalogue
> and repopulate it. The search is working fine now. You
> were right...I think the files were corrupted. We are
> still trying to find out how that happened.
> Thanks for your help. I will keep the SQL in case that
> happens again.
> Linda
> reference" a FT
> modification to both
> recommend that you
> BEFORE using the
> environment prior to using
> concerning
> freezing
> is
> query
> it.
> for
> near
> review
> drive)
> a
> as
> re-
> has
> and I
> during
> I
|||I would like a copy of that script if it's still
available! Thanks!
>--Original Message--
>Linda,
>I emailed you the SQL Server 7.0 version to "manually de-
reference" a FT
>Catalog, please use it with caution as it requires
modification to both
>system tables as well as the registry hive. I highly
recommend that you
>backup both your database as well as the registry hive
BEFORE using the
>script as well as testing the procedure in a test
environment prior to using[vbcol=seagreen]
>it.
>Regards,
>John
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...
concerning[vbcol=seagreen]
freezing[vbcol=seagreen]
is[vbcol=seagreen]
query[vbcol=seagreen]
it.[vbcol=seagreen]
for[vbcol=seagreen]
near[vbcol=seagreen]
review[vbcol=seagreen]
drive)[vbcol=seagreen]
a[vbcol=seagreen]
as[vbcol=seagreen]
re-[vbcol=seagreen]
has[vbcol=seagreen]
and I[vbcol=seagreen]
during[vbcol=seagreen]
I
>
>.
>
been working for a long time, however, it stopped and I
cannot seem to get it to repopulate. It stopped during an
incremental population. I have tried deleting it so I can
rebuild it, but whatever I try to do, I get the same
message: "Database is not full-text enabled yet". Can
anyone help?
Linda,
Could you review your server's Application Event log for any "Microsoft
Search" or MssCi source events (warnings, or errors) near the day & time
that the FT Catalog stopped working? Additionally, review the server System
Event log for any relate disk i/o warnings of low free disk space on both
your server's system disk drive (usually, the C:\ drive) or the drive where
the FT Catalog reside.
Most likely the FT Catalog is corrupt (and you may see a MssCi event with a
stack trace in it) and you may be in a "Catch-22" situation where you cannot
drop the FT Catalog (please try this), nor re-build it as well as not able
to run a Full or Incremental Population. IF so and depending upon the errors
in the Application event log, I have as sql script that you can "manually
de-reference" the FT Catalog, however, it is highly dependent on the type of
errors you are seeing and you may need to remove and re-install the FTS and
MSSearch components as well. Please, post any related application event
errors in your reply!
Thanks,
John
"Linda" <anonymous@.discussions.microsoft.com> wrote in message
news:2865701c46458$a8cf3cf0$a501280a@.phx.gbl...
> I have SQL Server 7 on an NT server. The catalogue has
> been working for a long time, however, it stopped and I
> cannot seem to get it to repopulate. It stopped during an
> incremental population. I have tried deleting it so I can
> rebuild it, but whatever I try to do, I get the same
> message: "Database is not full-text enabled yet". Can
> anyone help?
|||John,
I examined all logs but could not find anything concerning
the FT catalog. The logs for that date are no longer
available. It seems that the server was rebooted while
the catalog was performing an incremental update, freezing
the catalog.
I tried to drop it, but again got the message "Database is
not full-text enabled Please run
sp_fulltext_database 'enable' . When I do that, the query
never finishes. I have to reboot the server to clear it.
Maybe the script can help?
Thanks!!
Linda
>--Original Message--
>Linda,
>Could you review your server's Application Event log for
any "Microsoft
>Search" or MssCi source events (warnings, or errors) near
the day & time
>that the FT Catalog stopped working? Additionally, review
the server System
>Event log for any relate disk i/o warnings of low free
disk space on both
>your server's system disk drive (usually, the C:\ drive)
or the drive where
>the FT Catalog reside.
>Most likely the FT Catalog is corrupt (and you may see a
MssCi event with a
>stack trace in it) and you may be in a "Catch-22"
situation where you cannot
>drop the FT Catalog (please try this), nor re-build it as
well as not able
>to run a Full or Incremental Population. IF so and
depending upon the errors
>in the Application event log, I have as sql script that
you can "manually
>de-reference" the FT Catalog, however, it is highly
dependent on the type of
>errors you are seeing and you may need to remove and re-
install the FTS and
>MSSearch components as well. Please, post any related
application event
>errors in your reply!
>Thanks,
>John
>
>"Linda" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:2865701c46458$a8cf3cf0$a501280a@.phx.gbl...
an[vbcol=seagreen]
can
>
>.
>
|||Linda,
I emailed you the SQL Server 7.0 version to "manually de-reference" a FT
Catalog, please use it with caution as it requires modification to both
system tables as well as the registry hive. I highly recommend that you
backup both your database as well as the registry hive BEFORE using the
script as well as testing the procedure in a test environment prior to using
it.
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...[vbcol=seagreen]
> John,
> I examined all logs but could not find anything concerning
> the FT catalog. The logs for that date are no longer
> available. It seems that the server was rebooted while
> the catalog was performing an incremental update, freezing
> the catalog.
> I tried to drop it, but again got the message "Database is
> not full-text enabled Please run
> sp_fulltext_database 'enable' . When I do that, the query
> never finishes. I have to reboot the server to clear it.
> Maybe the script can help?
> Thanks!!
> Linda
> any "Microsoft
> the day & time
> the server System
> disk space on both
> or the drive where
> MssCi event with a
> situation where you cannot
> well as not able
> depending upon the errors
> you can "manually
> dependent on the type of
> install the FTS and
> application event
> message
> an
> can
|||John,
Before I received your SQL I tried something that worked.
Since I couldn't stop the MSSearch engine, I changed the
startup from automatic to manual. Then I rebooted the
server. With MSSearch service off, I was then able to
manipulate the gatherlogs so I copied the entire folders
to another directory (as a backup). Then I deleted the
original folders, started the service, and
ran "sp_fulltext_database 'enable'" which worked this
time. I was then able to rebuild the fulltext catalogue
and repopulate it. The search is working fine now. You
were right...I think the files were corrupted. We are
still trying to find out how that happened.
Thanks for your help. I will keep the SQL in case that
happens again.
Linda
>--Original Message--
>Linda,
>I emailed you the SQL Server 7.0 version to "manually de-
reference" a FT
>Catalog, please use it with caution as it requires
modification to both
>system tables as well as the registry hive. I highly
recommend that you
>backup both your database as well as the registry hive
BEFORE using the
>script as well as testing the procedure in a test
environment prior to using[vbcol=seagreen]
>it.
>Regards,
>John
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...
concerning[vbcol=seagreen]
freezing[vbcol=seagreen]
is[vbcol=seagreen]
query[vbcol=seagreen]
it.[vbcol=seagreen]
for[vbcol=seagreen]
near[vbcol=seagreen]
review[vbcol=seagreen]
drive)[vbcol=seagreen]
a[vbcol=seagreen]
as[vbcol=seagreen]
re-[vbcol=seagreen]
has[vbcol=seagreen]
and I[vbcol=seagreen]
during[vbcol=seagreen]
I
>
>.
>
|||You're welcome, Linda,
As they say, there are many ways to 'skin a cat' (not that i'm anti-cat ;-),
but there are many ways to solve a problem and to further mix my metaphors,
the proof is in the pudding, i.e., whatever works, go with it!
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:2d96a01c46a6d$2d545ea0$a501280a@.phx.gbl...[vbcol=seagreen]
> John,
> Before I received your SQL I tried something that worked.
> Since I couldn't stop the MSSearch engine, I changed the
> startup from automatic to manual. Then I rebooted the
> server. With MSSearch service off, I was then able to
> manipulate the gatherlogs so I copied the entire folders
> to another directory (as a backup). Then I deleted the
> original folders, started the service, and
> ran "sp_fulltext_database 'enable'" which worked this
> time. I was then able to rebuild the fulltext catalogue
> and repopulate it. The search is working fine now. You
> were right...I think the files were corrupted. We are
> still trying to find out how that happened.
> Thanks for your help. I will keep the SQL in case that
> happens again.
> Linda
> reference" a FT
> modification to both
> recommend that you
> BEFORE using the
> environment prior to using
> concerning
> freezing
> is
> query
> it.
> for
> near
> review
> drive)
> a
> as
> re-
> has
> and I
> during
> I
|||I would like a copy of that script if it's still
available! Thanks!
>--Original Message--
>Linda,
>I emailed you the SQL Server 7.0 version to "manually de-
reference" a FT
>Catalog, please use it with caution as it requires
modification to both
>system tables as well as the registry hive. I highly
recommend that you
>backup both your database as well as the registry hive
BEFORE using the
>script as well as testing the procedure in a test
environment prior to using[vbcol=seagreen]
>it.
>Regards,
>John
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:287e401c464fa$6a21ad10$a601280a@.phx.gbl...
concerning[vbcol=seagreen]
freezing[vbcol=seagreen]
is[vbcol=seagreen]
query[vbcol=seagreen]
it.[vbcol=seagreen]
for[vbcol=seagreen]
near[vbcol=seagreen]
review[vbcol=seagreen]
drive)[vbcol=seagreen]
a[vbcol=seagreen]
as[vbcol=seagreen]
re-[vbcol=seagreen]
has[vbcol=seagreen]
and I[vbcol=seagreen]
during[vbcol=seagreen]
I
>
>.
>
Subscribe to:
Posts (Atom)