Re: Wrong SQLSTATE for Native Error 2727

Yes, I understand that. The error is expected in this case. However, I expect
different SQLSTATE. If you read my original post again, you can see that I
was expecting 42S12.

--Aleksey

"Bei Zhu [MSFT]" wrote:

> You need to create index index_junk first, then you can alter it.
>
> "Aleksey Dmitriyev" <AlekseyDmitriyev@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:37C76DB7-59CC-4C63-BBF6-67ED7D9C2F81@xxxxxxxxxxxxxxxx
> > Steps to reproduce:
> >
> > 1) Execute this script using any tool
> > create table t1(a int)
> >
> > 2) Start ODBCTEST and login in to SQL Server. Run this query (I simply
> click
> > on the exclamation point)
> > alter index index_junk on t1 rebuild
> >
> > 3) Review the output:
> > Return: SQL_ERROR=-1
> > stmt:szSqlState = "42S21", *pfNativeError = 2727, *pcbErrorMsg = 73,
> > *ColumnNumber = -1, *RowNumber = 1
> > MessageText = "[Microsoft][SQL Native Client][SQL Server]Cannot find index
> > 'index_junk'."
> >
> > My configuration:
> > SQL Server 2005 IDW12 (I believe)
> > SQL Native Client dirver that comes with it.
> > The same error exist with I use SQL ODBC Driver that comes with MDAC 2.8.
> I
> > have not tried SQL Server 2000, but I believe this error code mapping
> occurs
> > in ODBC on the client side and Server should not make a difference.
> >
> >
> > --Aleksey
> >
> >
> >
> > "Bei Zhu [MSFT]" wrote:
> >
> > > Could you please provide more info? Like index_junk and table creation.
> > >
> > > "Aleksey Dmitriyev" <AlekseyDmitriyev@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> in
> > > message news:981E61BC-DB8B-4DE3-A21A-6FFEE2824DF2@xxxxxxxxxxxxxxxx
> > > > I get SQLSTATE 42S21 with native code 2727 when executing this query:
> > > >
> > > > alter index index_junk on testauto rebuild
> > > >
> > > > According to ODBC documentation the SQLSTATE should be 42S12 "Index
> not
> > > > found", not 42S21 "Column already exists". Is it a bug?
> > > >
> > > > --
> > > > -- Aleksey Dmitriyev
> > >
> > >
> > >
>
>
>
.

Relevant Pages

  • Re: Transaction problem (delete / select)
    ... It is not a bug. ... lock or a page lock during the delete. ... you are expecting SQL Server to look at data that will all be ...
    (microsoft.public.sqlserver.server)
  • Re: [PHP] is there a problem with php script pulling HTML out of database as it writes the page??
    ... them to know that addslashes is not adequate protection against SQL ... I even had one tell me "SQL injection? ... Surely you're being rhetorical, Stut, but no, you're not expecting too much. ...
    (php.general)
  • Re: Weight returning unexpected results
    ... the same statistics as 'regular' indexes, the concept of "update statistics" ... No, this is poorly doc'ed in the SQL 2000 BOL, I'm sad to say... ... > John, thanks for your reply. ... > was expecting. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: OpenRecordset anomaly
    ... --Mark Hammer ... if I copy the SQL from the Immediate window and paste it into ... expecting. ... a query having the identical SQL returns two records? ...
    (microsoft.public.access.queries)
  • Re: Connection Throttle
    ... we will refactor to Pervasive SQL ... >> actually expecting this to wait for the query to complete, ... We exported the database to another server (single ...
    (microsoft.public.sqlserver.server)
Loading