couldn't rename or delete maintenance plan in Management Studio

Hi,
I tried to rename and delete one old maintenance plan which is created by
other DBA and before the machine was renamed. But, I kept getting the
following error. I can rename and delete the maintenance plan I created.
An error has occurred while establishing a connection to the server. When
connecting to SQL server 2005, this failure may be cuased by the fact that
under the default settinfs SQL server does not allow remote connections
(provider: Named Pipes providers, error: 40 - could not open a connection to
SQL server) (Microsoft SQL server, Error: 53)
Shared Memory, TCP and Named Piples are all enabled.
Please advise.
Best Regards,
Lynn
I think the problem is that the maintenance plan use the Local Server
Connection which still point to the old machine name. (I couldn't move this
connection or modify the server name for this connection at all). I add
another connection, but I still couldn't delete this maintenance plan.
Please advise.
Best Regards,
Lynn
"Lynn" wrote:

> Hi,
> I tried to rename and delete one old maintenance plan which is created by
> other DBA and before the machine was renamed. But, I kept getting the
> following error. I can rename and delete the maintenance plan I created.
> An error has occurred while establishing a connection to the server. When
> connecting to SQL server 2005, this failure may be cuased by the fact that
> under the default settinfs SQL server does not allow remote connections
> (provider: Named Pipes providers, error: 40 - could not open a connection to
> SQL server) (Microsoft SQL server, Error: 53)
> Shared Memory, TCP and Named Piples are all enabled.
> Please advise.
> --
> Best Regards,
> Lynn
|||I've been pounding my head with a similar problem. A Server was renamed and
now I can't do anything with the plan.
Any more thoughts?
"Lynn" wrote:
[vbcol=seagreen]
> I think the problem is that the maintenance plan use the Local Server
> Connection which still point to the old machine name. (I couldn't move this
> connection or modify the server name for this connection at all). I add
> another connection, but I still couldn't delete this maintenance plan.
> Please advise.
> --
> Best Regards,
> Lynn
>
> "Lynn" wrote:

Could not open FCB for invalid file ID 20294 in database

Hi,
I am getting this error when I am trying to delete record
"Server: Msg 5180, Level 22, State 1, Line 1
Could not open FCB for invalid file ID 20294 in database 'SAS_Test'.
Connection Broken"
But when I use select command it works fine. I can ping the server, but some
how can't delete does not work!.
I check the SQL server log and it has "Could not open FCB for invalid file
ID 20294 in database, Error: 5180, Severity: 22, State: 1"
Any help would be appreciated.
Shan
Run DBCC CheckDB for that database to check physical corruption under file..
also refer to this link: -
http://support.microsoft.com/default...;en-us;Q276043
"Shan" wrote:

> Hi,
> I am getting this error when I am trying to delete record
> "Server: Msg 5180, Level 22, State 1, Line 1
> Could not open FCB for invalid file ID 20294 in database 'SAS_Test'.
> Connection Broken"
> But when I use select command it works fine. I can ping the server, but some
> how can't delete does not work!.
> I check the SQL server log and it has "Could not open FCB for invalid file
> ID 20294 in database, Error: 5180, Severity: 22, State: 1"
> Any help would be appreciated.
> --
> Shan

Could not open FCB for invalid file ID 20294 in database

Hi,
I am getting this error when I am trying to delete record
"Server: Msg 5180, Level 22, State 1, Line 1
Could not open FCB for invalid file ID 20294 in database 'SAS_Test'.
Connection Broken"
But when I use select command it works fine. I can ping the server, but some
how can't delete does not work!.
I check the SQL server log and it has "Could not open FCB for invalid file
ID 20294 in database, Error: 5180, Severity: 22, State: 1"
Any help would be appreciated.
--
ShanRun DBCC CheckDB for that database to check physical corruption under file..
also refer to this link: -
http://support.microsoft.com/defaul...b;en-us;Q276043
"Shan" wrote:

> Hi,
> I am getting this error when I am trying to delete record
> "Server: Msg 5180, Level 22, State 1, Line 1
> Could not open FCB for invalid file ID 20294 in database 'SAS_Test'.
> Connection Broken"
> But when I use select command it works fine. I can ping the server, but so
me
> how can't delete does not work!.
> I check the SQL server log and it has "Could not open FCB for invalid file
> ID 20294 in database, Error: 5180, Severity: 22, State: 1"
> Any help would be appreciated.
> --
> Shan

Could not open FCB for invalid file ID 20294 in database

Hi,
I am getting this error when I am trying to delete record
"Server: Msg 5180, Level 22, State 1, Line 1
Could not open FCB for invalid file ID 20294 in database 'SAS_Test'.
Connection Broken"
But when I use select command it works fine. I can ping the server, but some
how can't delete does not work!.
I check the SQL server log and it has "Could not open FCB for invalid file
ID 20294 in database, Error: 5180, Severity: 22, State: 1"
Any help would be appreciated.
--
ShanRun DBCC CheckDB for that database to check physical corruption under file..
also refer to this link: -
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q276043
"Shan" wrote:
> Hi,
> I am getting this error when I am trying to delete record
> "Server: Msg 5180, Level 22, State 1, Line 1
> Could not open FCB for invalid file ID 20294 in database 'SAS_Test'.
> Connection Broken"
> But when I use select command it works fine. I can ping the server, but some
> how can't delete does not work!.
> I check the SQL server log and it has "Could not open FCB for invalid file
> ID 20294 in database, Error: 5180, Severity: 22, State: 1"
> Any help would be appreciated.
> --
> Shan

could not disable publishing and distribution

hello All,

i am trying to delete publications in SQL 2000, SP4 and getting this
error:

SQL Server Enterprise Manager could not disable publishing and distribution on '<publishername>'.

Error 3724 : cannot drop the procedure
'dbo.sp_sel_F854ED4CD7EA4399EFDB9697F4E24A10_pal' because itis being used for replication.

Thanks and Regards

Kanna

Run sp_removedbreplication in the published database.

Could not continue scan with NOLOCK due to data movement. when delete a record

Error 601
Severity Level 12
Message Text
Could not continue scan with NOLOCK due to data movement.
My client always hit this error when he tried to delete a record from
table. The table contains about 1 million records. the table has a
unique index idx_1 on (col_a, col_b, col_c). non-unique index idx_2 on
(col_a),
non-unique index idx_3 on col_c. An update trigger on table also.
When he execute
delete from table_a where col_a = @.parm1 and col_c = @.parm3. he gets
the 601 error.
but if he execute
delete from table_a where col_a = @.parm1 and col_b = @.parm2. he can
delete this one record.
We execute dbcc checktable(table_a) and no error reported.
I read posts that saying it is because read-uncommitted or nolock
hint, but we do not has this options and we did not execute select
statement.
Any idea why this happens, we are afraid that the table is not healthy/
waiting to corruption. Is there anything we can do to narrow down
where the cause is and to provent it happen again?
and it is MS SQL 2000 with SP4
thanks in advance
-rockdaleDoes this KB article apply?
http://support.microsoft.com/kb/815008
Linchi
"rockdale" wrote:
> Error 601
> Severity Level 12
> Message Text
> Could not continue scan with NOLOCK due to data movement.
> My client always hit this error when he tried to delete a record from
> table. The table contains about 1 million records. the table has a
> unique index idx_1 on (col_a, col_b, col_c). non-unique index idx_2 on
> (col_a),
> non-unique index idx_3 on col_c. An update trigger on table also.
> When he execute
> delete from table_a where col_a = @.parm1 and col_c = @.parm3. he gets
> the 601 error.
> but if he execute
> delete from table_a where col_a = @.parm1 and col_b = @.parm2. he can
> delete this one record.
> We execute dbcc checktable(table_a) and no error reported.
> I read posts that saying it is because read-uncommitted or nolock
> hint, but we do not has this options and we did not execute select
> statement.
> Any idea why this happens, we are afraid that the table is not healthy/
> waiting to corruption. Is there anything we can do to narrow down
> where the cause is and to provent it happen again?
> and it is MS SQL 2000 with SP4
> thanks in advance
> -rockdale
>|||NOPE.
The database is SQL2K with SP4.
They did not execute any select statement, not mention Read Uncommited
option.
They execute the delete statement using one where condition and get
the error.
They execute the delete statement using another where condition and
no error occured.
I even execute the DBCC TRACEON (9134, -1) as the article you
mentioned, I still getting the same error. I can not restart the sql
server, it is a production server.
Thanks
On Oct 19, 11:46 am, Linchi Shea
<LinchiS...@.discussions.microsoft.com> wrote:
> Does this KB article apply?http://support.microsoft.com/kb/815008
> Linchi
>
> "rockdale" wrote:
> > Error 601
> > Severity Level 12
> > Message Text
> > Could not continue scan with NOLOCK due to data movement.
> > My client always hit this error when he tried to delete a record from
> > table. The table contains about 1 million records. the table has a
> > unique index idx_1 on (col_a, col_b, col_c). non-unique index idx_2 on
> > (col_a),
> > non-unique index idx_3 on col_c. An update trigger on table also.
> > When he execute
> > delete from table_a where col_a = @.parm1 and col_c = @.parm3. he gets
> > the 601 error.
> > but if he execute
> > delete from table_a where col_a = @.parm1 and col_b = @.parm2. he can
> > delete this one record.
> > We execute dbcc checktable(table_a) and no error reported.
> > I read posts that saying it is because read-uncommitted or nolock
> > hint, but we do not has this options and we did not execute select
> > statement.
> > Any idea why this happens, we are afraid that the table is not healthy/
> > waiting to corruption. Is there anything we can do to narrow down
> > where the cause is and to provent it happen again?
> > and it is MS SQL 2000 with SP4
> > thanks in advance
> > -rockdale- Hide quoted text -
> - Show quoted text -|||Look for a DELETE trigger on the table.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"rockdale" <rockdale.green@.gmail.com> wrote in message
news:1192807669.901836.228930@.i38g2000prf.googlegroups.com...
> Error 601
> Severity Level 12
> Message Text
> Could not continue scan with NOLOCK due to data movement.
> My client always hit this error when he tried to delete a record from
> table. The table contains about 1 million records. the table has a
> unique index idx_1 on (col_a, col_b, col_c). non-unique index idx_2 on
> (col_a),
> non-unique index idx_3 on col_c. An update trigger on table also.
> When he execute
> delete from table_a where col_a = @.parm1 and col_c = @.parm3. he gets
> the 601 error.
> but if he execute
> delete from table_a where col_a = @.parm1 and col_b = @.parm2. he can
> delete this one record.
> We execute dbcc checktable(table_a) and no error reported.
> I read posts that saying it is because read-uncommitted or nolock
> hint, but we do not has this options and we did not execute select
> statement.
> Any idea why this happens, we are afraid that the table is not healthy/
> waiting to corruption. Is there anything we can do to narrow down
> where the cause is and to provent it happen again?
> and it is MS SQL 2000 with SP4
> thanks in advance
> -rockdale
>|||They have a n update trigger in the table basically update the
lastedUpdateDateTime field. The Trigger is for Update only, so I do
not think delete will trigger this trigger.
On Oct 19, 1:30 pm, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Look for a DELETE trigger on the table.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
> "rockdale" <rockdale.gr...@.gmail.com> wrote in message
> news:1192807669.901836.228930@.i38g2000prf.googlegroups.com...
>
> > Error 601
> > Severity Level 12
> > Message Text
> > Could not continue scan with NOLOCK due to data movement.
> > My client always hit this error when he tried to delete a record from
> > table. The table contains about 1 million records. the table has a
> > unique index idx_1 on (col_a, col_b, col_c). non-unique index idx_2 on
> > (col_a),
> > non-unique index idx_3 on col_c. An update trigger on table also.
> > When he execute
> > delete from table_a where col_a = @.parm1 and col_c = @.parm3. he gets
> > the 601 error.
> > but if he execute
> > delete from table_a where col_a = @.parm1 and col_b = @.parm2. he can
> > delete this one record.
> > We execute dbcc checktable(table_a) and no error reported.
> > I read posts that saying it is because read-uncommitted or nolock
> > hint, but we do not has this options and we did not execute select
> > statement.
> > Any idea why this happens, we are afraid that the table is not healthy/
> > waiting to corruption. Is there anything we can do to narrow down
> > where the cause is and to provent it happen again?
> > and it is MS SQL 2000 with SP4
> > thanks in advance
> > -rockdale- Hide quoted text -
> - Show quoted text -|||I just delete the trigger and I still getting the same error.
More Info on index:
They have a UNIQUE NONCLUSTERED Constraints on table_a
(col_a, col_b, col_c)
an INDEX on table_a
(col_c)
an INDEX on table_a
(col_a)
Might these indices problems?
thanks
On Oct 19, 1:30 pm, "Geoff N. Hiten" <SQLCrafts...@.gmail.com> wrote:
> Look for a DELETE trigger on the table.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
> "rockdale" <rockdale.gr...@.gmail.com> wrote in message
> news:1192807669.901836.228930@.i38g2000prf.googlegroups.com...
>
> > Error 601
> > Severity Level 12
> > Message Text
> > Could not continue scan with NOLOCK due to data movement.
> > My client always hit this error when he tried to delete a record from
> > table. The table contains about 1 million records. the table has a
> > unique index idx_1 on (col_a, col_b, col_c). non-unique index idx_2 on
> > (col_a),
> > non-unique index idx_3 on col_c. An update trigger on table also.
> > When he execute
> > delete from table_a where col_a = @.parm1 and col_c = @.parm3. he gets
> > the 601 error.
> > but if he execute
> > delete from table_a where col_a = @.parm1 and col_b = @.parm2. he can
> > delete this one record.
> > We execute dbcc checktable(table_a) and no error reported.
> > I read posts that saying it is because read-uncommitted or nolock
> > hint, but we do not has this options and we did not execute select
> > statement.
> > Any idea why this happens, we are afraid that the table is not healthy/
> > waiting to corruption. Is there anything we can do to narrow down
> > where the cause is and to provent it happen again?
> > and it is MS SQL 2000 with SP4
> > thanks in advance
> > -rockdale- Hide quoted text -
> - Show quoted text -

Could CONTEXT_INFO persist across connections because of pooling?

i am issuing
SET CONTEXT_INFO @.BinarySoftwareUserIdentification
when i connect to the database so that later during my insert/update/delete
audit logging triggers i can get the user of the software that did the
modification.
Is it possible that a new connection could inherit the CONTEXT_INFO from an
old connection?
The situation is that the web-server itself is issuing all the connections,
so any connections made and dropped happen from the same machine. An
automated process on the server doesn't issue a call to SET CONTEXT_INFO
(for whatever reason). Could the pooled database connection that the process
gets have the same CONTEXT_INFO as the previous person who used that
connection?
Would SQL Server clear CONTEXT_INFO when a user using ADO closes their
connection? Or would it only get rid of it when the pool timeout finally
happens?
Put it another way, can one connection be impersonating the user who
previously owned that connection?Good question, Ian...
I never doubt the correctness of the author of this article:
http://www.sqldev.net/misc/sp_reset_connection.htm
It does say that sp_reset_connection does reset all SET options. However, CONTEXT_INFO could just be
a special case... I'd test it just to be certain. Note that the article specifies that the reset is
performed when the connection is *re-used* (lazy...).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ian Boyd" <ian.msnews010@.avatopia.com> wrote in message
news:%23KReMJceGHA.3388@.TK2MSFTNGP05.phx.gbl...
>i am issuing
> SET CONTEXT_INFO @.BinarySoftwareUserIdentification
> when i connect to the database so that later during my insert/update/delete audit logging triggers
> i can get the user of the software that did the modification.
> Is it possible that a new connection could inherit the CONTEXT_INFO from an old connection?
> The situation is that the web-server itself is issuing all the connections, so any connections
> made and dropped happen from the same machine. An automated process on the server doesn't issue a
> call to SET CONTEXT_INFO (for whatever reason). Could the pooled database connection that the
> process gets have the same CONTEXT_INFO as the previous person who used that connection?
> Would SQL Server clear CONTEXT_INFO when a user using ADO closes their connection? Or would it
> only get rid of it when the pool timeout finally happens?
>
> Put it another way, can one connection be impersonating the user who previously owned that
> connection?
>|||> I'd test it just to be certain.
i thought that trying to trick ADO into giving me the same pooled connection
would be like trying to get cats to walk in a line.
But my test program was
1. Open connection
2. Set Context info
3. Close connection
4. Open connection
5. Get Context info
i got the original context info back, and it turns out i (obviously) got the
same SPID both times. So, Microsoft, if you could update sp_reset_connection
in SQL Server X, that would be great.
And a service pack for SQL2000 would be nice too.|||> would be like trying to get cats to walk in a line.
I like the analogy... :-)
Thanks for letting us know that sp_reset_connection does not clear out CONTEXT_INFO. Seems like MS
missed that (I'd guess). Possibly because CONTEXT_INFO doesn't seem to be used very much.
> So, Microsoft, if you could update sp_reset_connection in SQL Server X, that would be great.
Did you do the feedback?
http://lab.msdn.microsoft.com/productfeedback/
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ian Boyd" <ian.msnews010@.avatopia.com> wrote in message
news:ukyJH5deGHA.3556@.TK2MSFTNGP02.phx.gbl...
>> I'd test it just to be certain.
> i thought that trying to trick ADO into giving me the same pooled connection would be like trying
> to get cats to walk in a line.
> But my test program was
> 1. Open connection
> 2. Set Context info
> 3. Close connection
> 4. Open connection
> 5. Get Context info
> i got the original context info back, and it turns out i (obviously) got the same SPID both times.
> So, Microsoft, if you could update sp_reset_connection in SQL Server X, that would be great.
> And a service pack for SQL2000 would be nice too.
>

Corrupted table?

We have a SQL Server 2000 database with a table we cannot delete. We first
try from Enterprise Manager, and then tried through VB code, and a stored
procedure, but nothing is able to delete the table. Is there anything else
to try?
Thank you.DROP TABLE <table name>.
But what is the error you get?
--
Jacco Schalkwijk
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Have you tried running DBCC CHECKTABLE?
--
Andrew J. Kelly SQL MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Hi,
First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
Take a backup of Database prior to execute DBCC with Repair options.
Thanks
Hari
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Actually, there is no error. Enterprise Manager just freezes, and we have to
stop the task. Query Analyzer, doing the DROP TABLE reacts the same way. We
give it several minutes to come back. It shouldnt' take more than 10 minutes
to drop a table.Maybe we can let it run ...'
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:eYQLnegQFHA.2132@.TK2MSFTNGP09.phx.gbl...
> DROP TABLE <table name>.
> But what is the error you get?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> > We have a SQL Server 2000 database with a table we cannot delete. We
first
> > try from Enterprise Manager, and then tried through VB code, and a
stored
> > procedure, but nothing is able to delete the table. Is there anything
else
> > to try?
> >
> > Thank you.
> >
> >
>|||That is not what MS recommends. You should not repair without first
determining root cause of the errors and then you should use a backup as the
best way to recover from the error (unless the only repair needed is to
rebuild indexes). Primairly though, you need to work out why the error
happened in the first place.
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
> Hi,
> First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
> REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
> Take a backup of Database prior to execute DBCC with Repair options.
> Thanks
> Hari
> SQL Server MVP
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> > We have a SQL Server 2000 database with a table we cannot delete. We
first
> > try from Enterprise Manager, and then tried through VB code, and a
stored
> > procedure, but nothing is able to delete the table. Is there anything
else
> > to try?
> >
> > Thank you.
> >
> >
>|||There is no error, we just can't drop the table. We've tried to delete the
table inside Enterprise Manager, from a VB program, and from Query Analyzer.
Each time when the command executes to drop the table, the program freezes,
and we have to stop the task. Maybe we should wait longer (10 minutes) to
see if an error eventually occurs, but after about 10 mins. there is no
error and the program stops responding to the request to drop the table.
I ran DBCC checkTable and there are no reported errors.
ANy ideas? Thanks!
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> That is not what MS recommends. You should not repair without first
> determining root cause of the errors and then you should use a backup as
the
> best way to recover from the error (unless the only repair needed is to
> rebuild indexes). Primairly though, you need to work out why the error
> happened in the first place.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
> > Hi,
> >
> > First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try
with
> > REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
> >
> > Take a backup of Database prior to execute DBCC with Repair options.
> >
> > Thanks
> > Hari
> > SQL Server MVP
> >
> > "Dean J Garrett" <info@.amuletc.com> wrote in message
> > news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> > > We have a SQL Server 2000 database with a table we cannot delete. We
> first
> > > try from Enterprise Manager, and then tried through VB code, and a
> stored
> > > procedure, but nothing is able to delete the table. Is there anything
> else
> > > to try?
> > >
> > > Thank you.
> > >
> > >
> >
> >
>|||Blocking? Did you check using sp_who, sp_who2 etc?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:epK3ZkFRFHA.1236@.TK2MSFTNGP14.phx.gbl...
> There is no error, we just can't drop the table. We've tried to delete the
> table inside Enterprise Manager, from a VB program, and from Query Analyzer.
> Each time when the command executes to drop the table, the program freezes,
> and we have to stop the task. Maybe we should wait longer (10 minutes) to
> see if an error eventually occurs, but after about 10 mins. there is no
> error and the program stops responding to the request to drop the table.
> I ran DBCC checkTable and there are no reported errors.
> ANy ideas? Thanks!
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
>> That is not what MS recommends. You should not repair without first
>> determining root cause of the errors and then you should use a backup as
> the
>> best way to recover from the error (unless the only repair needed is to
>> rebuild indexes). Primairly though, you need to work out why the error
>> happened in the first place.
>> Regards
>> --
>> Paul Randal
>> Dev Lead, Microsoft SQL Server Storage Engine
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
>> news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
>> > Hi,
>> >
>> > First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try
> with
>> > REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
>> >
>> > Take a backup of Database prior to execute DBCC with Repair options.
>> >
>> > Thanks
>> > Hari
>> > SQL Server MVP
>> >
>> > "Dean J Garrett" <info@.amuletc.com> wrote in message
>> > news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
>> > > We have a SQL Server 2000 database with a table we cannot delete. We
>> first
>> > > try from Enterprise Manager, and then tried through VB code, and a
>> stored
>> > > procedure, but nothing is able to delete the table. Is there anything
>> else
>> > > to try?
>> > >
>> > > Thank you.
>> > >
>> > >
>> >
>> >
>>
>

Corrupted table?

We have a SQL Server 2000 database with a table we cannot delete. We first
try from Enterprise Manager, and then tried through VB code, and a stored
procedure, but nothing is able to delete the table. Is there anything else
to try?
Thank you.
DROP TABLE <table name>.
But what is the error you get?
Jacco Schalkwijk
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>
|||Have you tried running DBCC CHECKTABLE?
Andrew J. Kelly SQL MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>
|||Hi,
First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
Take a backup of Database prior to execute DBCC with Repair options.
Thanks
Hari
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>
|||Actually, there is no error. Enterprise Manager just freezes, and we have to
stop the task. Query Analyzer, doing the DROP TABLE reacts the same way. We
give it several minutes to come back. It shouldnt' take more than 10 minutes
to drop a table.Maybe we can let it run ...?
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid > wrote
in message news:eYQLnegQFHA.2132@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> DROP TABLE <table name>.
> But what is the error you get?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
first[vbcol=seagreen]
stored[vbcol=seagreen]
else
>
|||That is not what MS recommends. You should not repair without first
determining root cause of the errors and then you should use a backup as the
best way to recover from the error (unless the only repair needed is to
rebuild indexes). Primairly though, you need to work out why the error
happened in the first place.
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Hi,
> First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
> REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
> Take a backup of Database prior to execute DBCC with Repair options.
> Thanks
> Hari
> SQL Server MVP
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
first[vbcol=seagreen]
stored[vbcol=seagreen]
else
>
|||There is no error, we just can't drop the table. We've tried to delete the
table inside Enterprise Manager, from a VB program, and from Query Analyzer.
Each time when the command executes to drop the table, the program freezes,
and we have to stop the task. Maybe we should wait longer (10 minutes) to
see if an error eventually occurs, but after about 10 mins. there is no
error and the program stops responding to the request to drop the table.
I ran DBCC checkTable and there are no reported errors.
ANy ideas? Thanks!
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> That is not what MS recommends. You should not repair without first
> determining root cause of the errors and then you should use a backup as
the
> best way to recover from the error (unless the only repair needed is to
> rebuild indexes). Primairly though, you need to work out why the error
> happened in the first place.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
with
> first
> stored
> else
>
|||Blocking? Did you check using sp_who, sp_who2 etc?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:epK3ZkFRFHA.1236@.TK2MSFTNGP14.phx.gbl...
> There is no error, we just can't drop the table. We've tried to delete the
> table inside Enterprise Manager, from a VB program, and from Query Analyzer.
> Each time when the command executes to drop the table, the program freezes,
> and we have to stop the task. Maybe we should wait longer (10 minutes) to
> see if an error eventually occurs, but after about 10 mins. there is no
> error and the program stops responding to the request to drop the table.
> I ran DBCC checkTable and there are no reported errors.
> ANy ideas? Thanks!
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> the
> rights.
> with
>

Corrupted table?

We have a SQL Server 2000 database with a table we cannot delete. We first
try from Enterprise Manager, and then tried through VB code, and a stored
procedure, but nothing is able to delete the table. Is there anything else
to try?
Thank you.DROP TABLE <table name>.
But what is the error you get?
Jacco Schalkwijk
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Have you tried running DBCC CHECKTABLE?
Andrew J. Kelly SQL MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Hi,
First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
Take a backup of Database prior to execute DBCC with Repair options.
Thanks
Hari
SQL Server MVP
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
> We have a SQL Server 2000 database with a table we cannot delete. We first
> try from Enterprise Manager, and then tried through VB code, and a stored
> procedure, but nothing is able to delete the table. Is there anything else
> to try?
> Thank you.
>|||Actually, there is no error. Enterprise Manager just freezes, and we have to
stop the task. Query Analyzer, doing the DROP TABLE reacts the same way. We
give it several minutes to come back. It shouldnt' take more than 10 minutes
to drop a table.Maybe we can let it run ...'
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote
in message news:eYQLnegQFHA.2132@.TK2MSFTNGP09.phx.gbl...
> DROP TABLE <table name>.
> But what is the error you get?
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
first[vbcol=seagreen]
stored[vbcol=seagreen]
else[vbcol=seagreen]
>|||That is not what MS recommends. You should not repair without first
determining root cause of the errors and then you should use a backup as the
best way to recover from the error (unless the only repair needed is to
rebuild indexes). Primairly though, you need to work out why the error
happened in the first place.
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
> Hi,
> First Execute DBCC CHECKTABLE(TABLENAME), If it gives error then try with
> REPAIR OPTIONS. See DBCC CHECKTABLE command in books online.
> Take a backup of Database prior to execute DBCC with Repair options.
> Thanks
> Hari
> SQL Server MVP
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:%23kZjFGgQFHA.1236@.TK2MSFTNGP14.phx.gbl...
first[vbcol=seagreen]
stored[vbcol=seagreen]
else[vbcol=seagreen]
>|||There is no error, we just can't drop the table. We've tried to delete the
table inside Enterprise Manager, from a VB program, and from Query Analyzer.
Each time when the command executes to drop the table, the program freezes,
and we have to stop the task. Maybe we should wait longer (10 minutes) to
see if an error eventually occurs, but after about 10 mins. there is no
error and the program stops responding to the request to drop the table.
I ran DBCC checkTable and there are no reported errors.
ANy ideas? Thanks!
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> That is not what MS recommends. You should not repair without first
> determining root cause of the errors and then you should use a backup as
the
> best way to recover from the error (unless the only repair needed is to
> rebuild indexes). Primairly though, you need to work out why the error
> happened in the first place.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:#rmRpFkQFHA.2876@.TK2MSFTNGP09.phx.gbl...
with[vbcol=seagreen]
> first
> stored
> else
>|||Blocking? Did you check using sp_who, sp_who2 etc?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dean J Garrett" <info@.amuletc.com> wrote in message news:epK3ZkFRFHA.1236@.TK2MSFTNGP14.phx.
gbl...
> There is no error, we just can't drop the table. We've tried to delete the
> table inside Enterprise Manager, from a VB program, and from Query Analyze
r.
> Each time when the command executes to drop the table, the program freezes
,
> and we have to stop the task. Maybe we should wait longer (10 minutes) to
> see if an error eventually occurs, but after about 10 mins. there is no
> error and the program stops responding to the request to drop the table.
> I ran DBCC checkTable and there are no reported errors.
> ANy ideas? Thanks!
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:uTAONbERFHA.1392@.TK2MSFTNGP10.phx.gbl...
> the
> rights.
> with
>