Error 954: Database has invalid schema - SQL2000

I'm restoring a database on another server, the restore from disk goes
through successfully, until I try to click on tables or views I get the
message below:
Error 954: Database 'dbname' has invalid schema
Thanks in advance for any help.ITDUDE27,
Are you using SharePoint and Small Business Server? If so, here are a
couple of links:
http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
I do have one weird thought: it sounds as if the file location for the files
in the database does not match the actual file locations of the mdf and/or
ldf. Did you use the MOVE option during the RESTORE in order to position
the files properly?
Other than that, I have no really useful suggestions.
RLF
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> I'm restoring a database on another server, the restore from disk goes
> through successfully, until I try to click on tables or views I get the
> message below:
> Error 954: Database 'dbname' has invalid schema
> Thanks in advance for any help.
>|||Thanks Russ.
I'am running SP on SBS 2003. my Live sharepoint site is running fine and I
was able to install SP 2.0 on another server and it came up fine. I trying to
restore a copy of the live db as test and that is what is causing the error.
I had seen the second link you refered too, it was not help full. The point
of this exercise is to restore the sp database using Enterprize manager and
query it and then map it as my SP content database.
I've tried the move command using osql with no success. I think you are
absoluty correct about the Move, I'm just not having any luck, which ever way
I restore the SP db I get the same message.
Thanks in advance for any other feedback.
"Russell Fields" wrote:
> ITDUDE27,
> Are you using SharePoint and Small Business Server? If so, here are a
> couple of links:
> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
> I do have one weird thought: it sounds as if the file location for the files
> in the database does not match the actual file locations of the mdf and/or
> ldf. Did you use the MOVE option during the RESTORE in order to position
> the files properly?
> Other than that, I have no really useful suggestions.
> RLF
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > Thanks in advance for any help.
> >
> >
>
>|||Russell,
Can you comfirm the syntax for me.
Current location: N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche.bak from other server
New location: N:\Program Files\Microsoft SQL Server\MSSQL\Data
RESTORE DATABASE avalanche_new FROM DISK = 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche.bak'
WITH
MOVE 'northwind' TO 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche_new.mdf'
MOVE 'northwind_log' TO 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche_log.ldf'
Thanks in advance.
"Russell Fields" wrote:
> ITDUDE27,
> Are you using SharePoint and Small Business Server? If so, here are a
> couple of links:
> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
> I do have one weird thought: it sounds as if the file location for the files
> in the database does not match the actual file locations of the mdf and/or
> ldf. Did you use the MOVE option during the RESTORE in order to position
> the files properly?
> Other than that, I have no really useful suggestions.
> RLF
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > Thanks in advance for any help.
> >
> >
>
>|||ITDUDE27,
Syntax looks correct, but the code does not match your spec. Compare:
N:\Program Files\Microsoft SQL Server\MSSQL\Data
N:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\avalanche_new.mdf
If N:\ is a network drive that is not a supported configuration for SQL
Server databases. You will need to place the database files on locally
attached storage or on your SAN.
And, of course, I assume that the 'northwind%' logical names are correct.
I also usually specify a couple of things that should not be necessary in my
RESTORE command. Habit, you know, but I include the options:
RECOVERY, REPLACE
FWIW,
RLF
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:F7C1965F-448C-44F1-8DEF-9860E15E1A86@.microsoft.com...
> Russell,
> Can you comfirm the syntax for me.
> Current location: N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche.bak from other server
> New location: N:\Program Files\Microsoft SQL Server\MSSQL\Data
>
> RESTORE DATABASE avalanche_new FROM DISK = 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche.bak'
> WITH
> MOVE 'northwind' TO 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche_new.mdf'
> MOVE 'northwind_log' TO 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche_log.ldf'
> Thanks in advance.
>
> "Russell Fields" wrote:
>> ITDUDE27,
>> Are you using SharePoint and Small Business Server? If so, here are a
>> couple of links:
>> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
>> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
>> I do have one weird thought: it sounds as if the file location for the
>> files
>> in the database does not match the actual file locations of the mdf
>> and/or
>> ldf. Did you use the MOVE option during the RESTORE in order to position
>> the files properly?
>> Other than that, I have no really useful suggestions.
>> RLF
>> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
>> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
>> > I'm restoring a database on another server, the restore from disk goes
>> > through successfully, until I try to click on tables or views I get the
>> > message below:
>> >
>> > Error 954: Database 'dbname' has invalid schema
>> >
>> > Thanks in advance for any help.
>> >
>> >
>>

Error 954: Database 'dbname' has invalid schema

I'm restoring a database on another server, the restore from disk goes
through successfully, until I try to click on tables or views I get the
message below:
Error 954: Database 'dbname' has invalid schema
any thoughts?Hi
Can you provide us with more info? What is the version are you using? Do you
try restore from SS2000 to SS2005?
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:35AE8C40-3659-44DB-BABB-8B65D1223181@.microsoft.com...
> I'm restoring a database on another server, the restore from disk goes
> through successfully, until I try to click on tables or views I get the
> message below:
> Error 954: Database 'dbname' has invalid schema
> any thoughts?|||Thanks for the response uri.
I'm doing the restore on SS2000 to SS2000. I'm trying to test the install of
WSS3.0 on a test environment but the restore is displaying that error.
Thanks in advance.
"Uri Dimant" wrote:
> Hi
> Can you provide us with more info? What is the version are you using? Do you
> try restore from SS2000 to SS2005?
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:35AE8C40-3659-44DB-BABB-8B65D1223181@.microsoft.com...
> >
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > any thoughts?
>
>

error 823

hi!!!
i have this error 823, when i choise tables in a database, the description is input output error bad page id was detected during ...
if you have any sugections to recovery database, i'm great for them
thanks
manuel ralha
http://www.karaszi.com/sqlserver/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:66C39796-BD18-4E6C-AED0-DB07AF001973@.microsoft.com...
> hi!!!
> i have this error 823, when i choise tables in a database, the description is input output error bad page id
was detected during ...
> if you have any sugections to recovery database, i'm great for them
> thanks
> manuel ralha
|||hi, thanks
thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
thanks
manuel ralha
|||You didn't say which advice you followed.
Are you saying that you restore the latest clean db backup and all subsequent log backups and one of the log
backups re-introduced the corruption?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:371F4671-4653-4A3A-923C-22790C47AD7E@.microsoft.com...
> hi, thanks
> thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
> thanks
> manuel ralha
|||hi:
the error is this in query analiser or in osql:
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
manuel ralha
|||What I'm trying to communicate is (as is the article on the web site I suggested) that your best option is
probably to use your backups to restore a clean database, If you feel uncertain about the actions to take, I
suggest you let MS Support help you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:8A7D909A-E787-419A-B926-CA0323CF1600@.microsoft.com...
> hi:
> the error is this in query analiser or in osql:
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
> manuel ralha
>
|||hi
thanks for your help, i'm read your web page, and, i follow all steps. but unhappyly, thoesn't work in this database, i have the same errors.
thanks for your collaboration and help.
manuel ralha

error 823

hi!!
i have this error 823, when i choise tables in a database, the description is input output error bad page id was detected during ..
if you have any sugections to recovery database, i'm great for the
thank
manuel ralhahttp://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:66C39796-BD18-4E6C-AED0-DB07AF001973@.microsoft.com...
> hi!!!
> i have this error 823, when i choise tables in a database, the description is input output error bad page id
was detected during ...
> if you have any sugections to recovery database, i'm great for them
> thanks
> manuel ralha|||hi, thank
thats a good idea, but when i execute de dbcc checkdb , the error ocurs agai
thank
manuel ralha|||You didn't say which advice you followed.
Are you saying that you restore the latest clean db backup and all subsequent log backups and one of the log
backups re-introduced the corruption?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:371F4671-4653-4A3A-923C-22790C47AD7E@.microsoft.com...
> hi, thanks
> thats a good idea, but when i execute de dbcc checkdb , the error ocurs again
> thanks
> manuel ralha|||What I'm trying to communicate is (as is the article on the web site I suggested) that your best option is
probably to use your backups to restore a clean database, If you feel uncertain about the actions to take, I
suggest you let MS Support help you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"manuel ralha" <mralha@.foruminformatica.pt> wrote in message
news:8A7D909A-E787-419A-B926-CA0323CF1600@.microsoft.com...
> hi:
> the error is this in query analiser or in osql:
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in file 'D:\cedile\cedile_data.mdf'
> manuel ralha
>|||hi
thanks for your help, i'm read your web page, and, i follow all steps. but unhappyly, thoesn't work in this database, i have the same errors
thanks for your collaboration and help
manuel ralha

Error 8102:cannot update identity column

I set up replication on my DB between two server. The Publisher will not update tables on the Subscriber that use an identity column and I get an error"8102:cannot update identity column". I have looked around and can't seem to locate any solid fixes. If I remove the identity column from the subscribers tables the package works, but I am not able to use the DB on the subscriber because I need the Identity columns for my app to function properly. My Publisher and Subscriber are both running SQL Server 2000 Standard Edition SP3.

Thanks.Check out this MSDN Article:Replication: Managing Identity Values.

Terri|||Thanks for the reply, I already read this article and it solves the problem but creates another. The article does describe how to increment the Identity column on the subscriber, but it will not match the value on the publisher because you must set the ID column ranges in seperate blocks. Server P 1-1000 Server S 1001-2000 When 1 is used on P, it insert 1001 on S.

Here's what I'm doing and maybe there is another way to do it.

I have two servers running my application, 1 exposed to the Internet for client access and one for my Intranet. I need an exact replica of my database on the Internet server that is being updated periodically from my Intranet server. I am installing clustered servers soon but I need to have an interim solution in place until then. The publically exposed server is also to act as a backup in the event that my Intranet server goes down.

The database is currently being replicated between the servers, but the Identity columns on the subscriber are not set, so if we had to switch to it I would have to define the ID columns in my tables for my application to work properly.

Would it be okay to point my Internet servers WEB.CONFIG data connection string to the Intranet server and just allow the replication to continue as is, and if I do have an outage direct my Intranet traffic to the Internet server, change the conn string in the WEB.CONFIG and define the ID columns?

Thanks in advance.|||Is your Internet server then serving as a warm standby? Is it then basically a read-only version of the database on your Intranet server??

If so, I can telll you that we usetransaction log shipping to keep a warm standby of our database on a different server.

Otherwise, I'm sorry, replication is out of my league. We had used replication for a short while until we found out that it did not meet our needs (due in part to the IDENTITY column situation). With some research and effort we might have gotten replication to work, but log shipping was exactly right for us.

Terri
PS, if you haven't seen it, you might consider this article:Architecting Replication with Identity Columns
|||Transaction logs would work if I had the Enterprise version of SQL, but I won't have it for a few more months, at which point I am installing clustered servers. I think for the time being I am going to go with allowing it to replicate with no ID columns set on the subscriber. I only have 5, so if there was a problem I could just set the ID columns on the subscriber and then change my DB Connection in my WEB.CONFIG to point to it. This is however a temporary solution.

Thanks, I found your info most helpful.

Error 7347

We are getting Error 7347 error while querying via link server to Sybase. No
w this error is produced only in case of few tables. Query for other tables
is fine. There is another link server to the same sybase server but to a dif
ferent database and that it
fine.
Any help is appreciated
Here is the complete error message
****************************************
Server: Msg 7347, Level 16, State 1, Line 1
OLE DB provider 'Sybase.ASEOLEDBProvider' returned an unexpected data length
for the fixed-length column '[pds].[pds].[dbo].[product].cu
stodian_code'. The expected data length is 15, while the returned data lengt
h is 4.
OLE DB error trace [Non-interface error: Unexpected data length returne
d for the column: ProviderName='Sybase.ASEOLEDBProvider', TableName='[p
ds].[pds].[dbo].[product]', ColumnName='custodian_code', Expecte
dLength='15', ReturnedLength='4'].Hi,
////
The IDENTITY function should be used only when the SELECT statement has an
INTO clause.
Explanation:
Command failed due to invalid or illegal request. Check syntax, semantics,
and permissions. Take any corrective action indicated by message.
////
The sybase manual gives this explanation for the Error number 7347.I dont
know what query u are firing onto the server but just check if u are missing
something specified in the explanation
regards
Dilish
"Nishu" <anonymous@.discussions.microsoft.com> wrote in message
news:A98F91AB-9EFB-4F31-9281-2407BB0D2BE7@.microsoft.com...
> We are getting Error 7347 error while querying via link server to Sybase.
Now this error is produced only in case of few tables. Query for other
tables is fine. There is another link server to the same sybase server but
to a different database and that it fine.
> Any help is appreciated
>
> Here is the complete error message
> ****************************************
> Server: Msg 7347, Level 16, State 1, Line 1
> OLE DB provider 'Sybase.ASEOLEDBProvider' returned an unexpected data
length for the fixed-length column
'[pds].[pds].[dbo].[product].custodian_code'. The expected d
ata length is
15, while the returned data length is 4.
> OLE DB error trace [Non-interface error: Unexpected data length returned[/col
or]
for the column: ProviderName='Sybase.ASEOLEDBProvider',
TableName='[pds].[pds].[dbo].[product]', ColumnName='custodi
an_code',
ExpectedLength='15', ReturnedLength='4'].

Error 7317 when Accessing Linked Oracle Server

I have a linked server to an Oracle 8i database. When I attempt to query th
e
Oracle tables I get the following error:
Server: Msg 7317, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' returned an invalid schema definition.
OLE DB error trace [Non-interface error: OLE/DB provider returned an
invalid schema definition.].
The problem is occurring at my customer's site. I have tried duplicating
their environment in my office, but I can not reporduce the problem.
I would appreciate any help you could offer.
Thanks,
Bill Manring
Chief Software Architect
Wavefront Software, Inc.I found an answer to this problem so I thought I should post it in case
anyone else has a similar problem.
If I execute the query using the OPENQUERY function, the query executes
properly. Since OPENQUERY is a peferred way of querying linked srevers
anyway, there really is no problem.
"Bill Manring" wrote:

> I have a linked server to an Oracle 8i database. When I attempt to query
the
> Oracle tables I get the following error:
> Server: Msg 7317, Level 16, State 1, Line 1
> OLE DB provider 'MSDAORA' returned an invalid schema definition.
> OLE DB error trace [Non-interface error: OLE/DB provider returned an
> invalid schema definition.].
> The problem is occurring at my customer's site. I have tried duplicating
> their environment in my office, but I can not reporduce the problem.
> I would appreciate any help you could offer.
>
> --
> Thanks,
> Bill Manring
> Chief Software Architect
> Wavefront Software, Inc.

Error 7317 when Accessing Linked Oracle Server

I have a linked server to an Oracle 8i database. When I attempt to query the
Oracle tables I get the following error:
Server: Msg 7317, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' returned an invalid schema definition.
OLE DB error trace [Non-interface error: OLE/DB provider returned an
invalid schema definition.].
The problem is occurring at my customer's site. I have tried duplicating
their environment in my office, but I can not reporduce the problem.
I would appreciate any help you could offer.
Thanks,
Bill Manring
Chief Software Architect
Wavefront Software, Inc.
I found an answer to this problem so I thought I should post it in case
anyone else has a similar problem.
If I execute the query using the OPENQUERY function, the query executes
properly. Since OPENQUERY is a peferred way of querying linked srevers
anyway, there really is no problem.
"Bill Manring" wrote:

> I have a linked server to an Oracle 8i database. When I attempt to query the
> Oracle tables I get the following error:
> Server: Msg 7317, Level 16, State 1, Line 1
> OLE DB provider 'MSDAORA' returned an invalid schema definition.
> OLE DB error trace [Non-interface error: OLE/DB provider returned an
> invalid schema definition.].
> The problem is occurring at my customer's site. I have tried duplicating
> their environment in my office, but I can not reporduce the problem.
> I would appreciate any help you could offer.
>
> --
> Thanks,
> Bill Manring
> Chief Software Architect
> Wavefront Software, Inc.

Error 7105, how to fix it?

Hi
I am getting error 7105 Severity: 22 on one of my tables (about 1000
record), It seems 2 of the records has been corrupted. I can select other
records and edit the records as long as these 2 records are not part of
select query.
I have read microsoft support and they say that service pack2 should solve
this problem but my server already has service pack 3.
I can not choose these records to delete it, what is the solution, any idea?> I am getting error 7105 Severity: 22 on one of my tables (about 1000
> record), It seems 2 of the records has been corrupted. I can select other
> records and edit the records as long as these 2 records are not part of
> select query.
> I have read microsoft support and they say that service pack2 should solve
> this problem but my server already has service pack 3.
> I can not choose these records to delete it, what is the solution, any
idea?
What does DBCC CHECKDB report?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Error 7105, how to fix it?

Hi
I am getting error 7105 Severity: 22 on one of my tables (about 1000
record), It seems 2 of the records has been corrupted. I can select other
records and edit the records as long as these 2 records are not part of
select query.
I have read microsoft support and they say that service pack2 should solve
this problem but my server already has service pack 3.
I can not choose these records to delete it, what is the solution, any idea?> I am getting error 7105 Severity: 22 on one of my tables (about 1000
> record), It seems 2 of the records has been corrupted. I can select other
> records and edit the records as long as these 2 records are not part of
> select query.
> I have read microsoft support and they say that service pack2 should solve
> this problem but my server already has service pack 3.
> I can not choose these records to delete it, what is the solution, any
idea?
What does DBCC CHECKDB report?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Error 3624 Location: fakerowset.cpp:251

Hello,
I have the following error when I want to access the design
mode in Entreprise Manager of some tables :
Microsoft SQL-DMO (ODBC SQLState: HY000)
Error: 3624
Expression: accCategory == ACC_CATEGORY_NORMAL || accCatgegory ==
ACC_CATEGORY_BIT
SOPID: 52
Process ID : 2876
I'm running SQL server 2000 with SP3a.
Thanks for your help
You seem to be running into some sort of ASSERT is what I think. Please run
checkdb on your database, and check on the SQL error logs for any stack
dumps. Please paste the input buffer and short stack dump in this thread
and we can analyse.
Also if corruption is the cause, you also want to get your hw vendors
thoroughly involved and have them check your disk, controllers, etc.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Error 3624 Location: fakerowset.cpp:251

Hello,
I have the following error when I want to access the design
mode in Entreprise Manager of some tables :
Microsoft SQL-DMO (ODBC SQLState: HY000)
Error: 3624
Expression: accCategory == ACC_CATEGORY_NORMAL || accCatgegory == ACC_CATEGORY_BIT
SOPID: 52
Process ID : 2876
I'm running SQL server 2000 with SP3a.
Thanks for your helpYou seem to be running into some sort of ASSERT is what I think. Please run
checkdb on your database, and check on the SQL error logs for any stack
dumps. Please paste the input buffer and short stack dump in this thread
and we can analyse.
Also if corruption is the cause, you also want to get your hw vendors
thoroughly involved and have them check your disk, controllers, etc.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

ERROR 3027: CAN'T UPDATE

I IMPORTED A DATABASE FROM AN SQL SERVER 7.0 TO AN SQL
SERVER 2000. I CAN UPDATE THE TABLES DIRECTLY ON THE
SERVER, BUT WHEN I TRY TO DO IT WITH THE PROGRAM THAT USES
THE DATABASE, IT GIVES ME ERROR 3027: CAN'T UPDATE,
DATABASE OR OBJECT IS READ-ONLY. I HAVE GIVEN ALL THE
USERS THEIR RESPECTIVE RIGHTS ON THE NEW SERVER AND IN THE
DATABASE. I HAVE AN ".INI" FILE WHERE I CAN SET THE
SERVERNAME. DOES SOMEONE KNOW HOW TO SOLVE THIS.
Where are you getting the error and what is the full error
message? What is the programming language, API used to
access the database? Are you getting a 'Run-time error
'3027'? In that case, try adding a LockEdits property to the
OpenRecordset method if that's what the application is
using. Make sure you have primary keys or unique constraints
defined for the tables.
-Sue
On Fri, 6 Aug 2004 09:06:36 -0700, "SJURIC"
<SJURIC.STATIE@.AN.XACO.XEROX.COM> wrote:

>I IMPORTED A DATABASE FROM AN SQL SERVER 7.0 TO AN SQL
>SERVER 2000. I CAN UPDATE THE TABLES DIRECTLY ON THE
>SERVER, BUT WHEN I TRY TO DO IT WITH THE PROGRAM THAT USES
>THE DATABASE, IT GIVES ME ERROR 3027: CAN'T UPDATE,
>DATABASE OR OBJECT IS READ-ONLY. I HAVE GIVEN ALL THE
>USERS THEIR RESPECTIVE RIGHTS ON THE NEW SERVER AND IN THE
>DATABASE. I HAVE AN ".INI" FILE WHERE I CAN SET THE
>SERVERNAME. DOES SOMEONE KNOW HOW TO SOLVE THIS.
|||Thank you Sue. I discovered it was the Primary Keys that were not
transported along with the database when I wasn't logged on as the
administrator. My login has administrative rights, but it seems like
it's not the same as login in as the administrator. I couldn't thank you
earlier, because we were disconnected waiting on the new shields and
antivirus to arrive. Thanks again!
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

ERROR 3027: CAN'T UPDATE

I IMPORTED A DATABASE FROM AN SQL SERVER 7.0 TO AN SQL
SERVER 2000. I CAN UPDATE THE TABLES DIRECTLY ON THE
SERVER, BUT WHEN I TRY TO DO IT WITH THE PROGRAM THAT USES
THE DATABASE, IT GIVES ME ERROR 3027: CAN'T UPDATE,
DATABASE OR OBJECT IS READ-ONLY. I HAVE GIVEN ALL THE
USERS THEIR RESPECTIVE RIGHTS ON THE NEW SERVER AND IN THE
DATABASE. I HAVE AN ".INI" FILE WHERE I CAN SET THE
SERVERNAME. DOES SOMEONE KNOW HOW TO SOLVE THIS.Where are you getting the error and what is the full error
message? What is the programming language, API used to
access the database? Are you getting a 'Run-time error
'3027'? In that case, try adding a LockEdits property to the
OpenRecordset method if that's what the application is
using. Make sure you have primary keys or unique constraints
defined for the tables.
-Sue
On Fri, 6 Aug 2004 09:06:36 -0700, "SJURIC"
<SJURIC.STATIE@.AN.XACO.XEROX.COM> wrote:

>I IMPORTED A DATABASE FROM AN SQL SERVER 7.0 TO AN SQL
>SERVER 2000. I CAN UPDATE THE TABLES DIRECTLY ON THE
>SERVER, BUT WHEN I TRY TO DO IT WITH THE PROGRAM THAT USES
>THE DATABASE, IT GIVES ME ERROR 3027: CAN'T UPDATE,
>DATABASE OR OBJECT IS READ-ONLY. I HAVE GIVEN ALL THE
>USERS THEIR RESPECTIVE RIGHTS ON THE NEW SERVER AND IN THE
>DATABASE. I HAVE AN ".INI" FILE WHERE I CAN SET THE
>SERVERNAME. DOES SOMEONE KNOW HOW TO SOLVE THIS.|||Thank you Sue. I discovered it was the Primary Keys that were not
transported along with the database when I wasn't logged on as the
administrator. My login has administrative rights, but it seems like
it's not the same as login in as the administrator. I couldn't thank you
earlier, because we were disconnected waiting on the new shields and
antivirus to arrive. Thanks again!
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Error 2535

Hi All
For the pass two weeks, the DBCC CHECKTABLE with REPAIR_REBUILD option is coming out with error 2535 on certain tables. We are using SQL7 with Serive Pack 4. Please help
Thanks
MaryDear Mary
Explanatio
The DBCC CHECKALLOC statement detected a mismatch in the object ID between an allocation structure (extent) and sysindexes
Note Occasionally, DBCC CHECKALLOC reports this error when no real error condition exists. Execute DBCC CHECKALLOC in single-user mode if you suspect the 2535 error is incorrect
Actio
Follow these steps:
Examine the index ID associated with the page number in the message to determine whether the error occurred on the table data or on an index.
Restore the database:
If the object ID is less than or equal to 100, the error is on a system table. Restore the database from a clean backup
If the object ID is greater than 100, the error is on a user table
If this error occurs on table data (the index ID = 1), restore the database from a clean backup
If the error occurs on an index, you can usually correct it by dropping and re-creating the index. If dropping and re-creating the index is not feasible, or if you cannot drop the index, contact your primary support provider for assistance.
If the problem persists, contact your primary support provider for assistance. Have the output of the appropriate DBCC statements available for review
Faheem latif
NETSOL|||Dear Mary
Explanatio
The DBCC CHECKALLOC statement detected a mismatch in the object ID between an allocation structure (extent) and sysindexes
Note Occasionally, DBCC CHECKALLOC reports this error when no real error condition exists. Execute DBCC CHECKALLOC in single-user mode if you suspect the 2535 error is incorrect
Actio
Follow these steps:
Examine the index ID associated with the page number in the message to determine whether the error occurred on the table data or on an index.
Restore the database:
If the object ID is less than or equal to 100, the error is on a system table. Restore the database from a clean backup
If the object ID is greater than 100, the error is on a user table
If this error occurs on table data (the index ID = 1), restore the database from a clean backup
If the error occurs on an index, you can usually correct it by dropping and re-creating the index. If dropping and re-creating the index is not feasible, or if you cannot drop the index, contact your primary support provider for assistance.
If the problem persists, contact your primary support provider for assistance. Have the output of the appropriate DBCC statements available for review
Faheem Lati
NETSOL

Error 2535

Hi All,
For the pass two weeks, the DBCC CHECKTABLE with REPAIR_REBUILD option is coming out with error 2535 on certain tables. We are using SQL7 with Serive Pack 4. Please help.
Thanks,
Mary
Dear Mary,
Explanation
The DBCC CHECKALLOC statement detected a mismatch in the object ID between an allocation structure (extent) and sysindexes.
Note Occasionally, DBCC CHECKALLOC reports this error when no real error condition exists. Execute DBCC CHECKALLOC in single-user mode if you suspect the 2535 error is incorrect.
Action
Follow these steps:
Examine the index ID associated with the page number in the message to determine whether the error occurred on the table data or on an index.
Restore the database:
If the object ID is less than or equal to 100, the error is on a system table. Restore the database from a clean backup.
If the object ID is greater than 100, the error is on a user table.
If this error occurs on table data (the index ID = 1), restore the database from a clean backup.
If the error occurs on an index, you can usually correct it by dropping and re-creating the index. If dropping and re-creating the index is not feasible, or if you cannot drop the index, contact your primary support provider for assistance.
If the problem persists, contact your primary support provider for assistance. Have the output of the appropriate DBCC statements available for review.
Faheem latif
NETSOL
|||Dear Mary,
Explanation
The DBCC CHECKALLOC statement detected a mismatch in the object ID between an allocation structure (extent) and sysindexes.
Note Occasionally, DBCC CHECKALLOC reports this error when no real error condition exists. Execute DBCC CHECKALLOC in single-user mode if you suspect the 2535 error is incorrect.
Action
Follow these steps:
Examine the index ID associated with the page number in the message to determine whether the error occurred on the table data or on an index.
Restore the database:
If the object ID is less than or equal to 100, the error is on a system table. Restore the database from a clean backup.
If the object ID is greater than 100, the error is on a user table.
If this error occurs on table data (the index ID = 1), restore the database from a clean backup.
If the error occurs on an index, you can usually correct it by dropping and re-creating the index. If dropping and re-creating the index is not feasible, or if you cannot drop the index, contact your primary support provider for assistance.
If the problem persists, contact your primary support provider for assistance. Have the output of the appropriate DBCC statements available for review.
Faheem Latif
NETSOL
|||Faheem,
The object ID is greater than 100, see below, but what are the steps to fix the user table? Do I use bcp to outload the data, drop table, then load the data back?
Table Corrupt: Page (1:566656) is allocated to object ID 1189579276, index ID 255, not to object ID 798625888, index ID 5 found in page header.
Mary

Error 2535

Hi All,
For the pass two weeks, the DBCC CHECKTABLE with REPAIR_REBUILD option is co
ming out with error 2535 on certain tables. We are using SQL7 with Serive Pa
ck 4. Please help.
Thanks,
MaryDear Mary,
Explanation
The DBCC CHECKALLOC statement detected a mismatch in the object ID between a
n allocation structure (extent) and sysindexes.
Note Occasionally, DBCC CHECKALLOC reports this error when no real error co
ndition exists. Execute DBCC CHECKALLOC in single-user mode if you suspect t
he 2535 error is incorrect.
Action
Follow these steps:
Examine the index ID associated with the page number in the message to deter
mine whether the error occurred on the table data or on an index.
Restore the database:
If the object ID is less than or equal to 100, the error is on a system tabl
e. Restore the database from a clean backup.
If the object ID is greater than 100, the error is on a user table.
If this error occurs on table data (the index ID = 1), restore the database
from a clean backup.
If the error occurs on an index, you can usually correct it by dropping and
re-creating the index. If dropping and re-creating the index is not feasible
, or if you cannot drop the index, contact your primary support provider for
assistance.
If the problem persists, contact your primary support provider for assistanc
e. Have the output of the appropriate DBCC statements available for review.
Faheem latif
NETSOL|||Dear Mary,
Explanation
The DBCC CHECKALLOC statement detected a mismatch in the object ID between a
n allocation structure (extent) and sysindexes.
Note Occasionally, DBCC CHECKALLOC reports this error when no real error co
ndition exists. Execute DBCC CHECKALLOC in single-user mode if you suspect t
he 2535 error is incorrect.
Action
Follow these steps:
Examine the index ID associated with the page number in the message to deter
mine whether the error occurred on the table data or on an index.
Restore the database:
If the object ID is less than or equal to 100, the error is on a system tabl
e. Restore the database from a clean backup.
If the object ID is greater than 100, the error is on a user table.
If this error occurs on table data (the index ID = 1), restore the database
from a clean backup.
If the error occurs on an index, you can usually correct it by dropping and
re-creating the index. If dropping and re-creating the index is not feasible
, or if you cannot drop the index, contact your primary support provider for
assistance.
If the problem persists, contact your primary support provider for assistanc
e. Have the output of the appropriate DBCC statements available for review.
Faheem Latif
NETSOL|||Faheem,
The object ID is greater than 100, see below, but what are the steps to fix
the user table? Do I use bcp to outload the data, drop table, then load the
data back?
Table Corrupt: Page (1:566656) is allocated to object ID 1189579276, index I
D 255, not to object ID 798625888, index ID 5 found in page header.
Mary

Error 229: Permissions problem with sysobjects and sysindexes

Hi,
I'm trying to view a database using Enterprise Manager and am getting the
following error when I try to view the list of tables, stored procs etc:
Error 229: SELECT permission denied on object 'sysobjects', database
'tours180805', owner 'dbo'.
SELECT permission denied on object 'sysindexes', database 'tours180805',
owner 'dbo'.
I'm not actually the administrator of this database, and all I know is that
it's a snapshot of a live database setup for me to develop against while i'm
writing a B2B link. As such I don't know what method was used to make the
copy, and if anything has been left out during copying. I don't have these
problems when viewing the live version.
Any help gratefully received.
Ben FidgeBen Fidge (BenFidge@.discussions.microsoft.com) writes:
> I'm trying to view a database using Enterprise Manager and am getting the
> following error when I try to view the list of tables, stored procs etc:
> Error 229: SELECT permission denied on object 'sysobjects', database
> 'tours180805', owner 'dbo'.
> SELECT permission denied on object 'sysindexes', database 'tours180805',
> owner 'dbo'.
> I'm not actually the administrator of this database, and all I know is
> that it's a snapshot of a live database setup for me to develop against
> while i'm writing a B2B link. As such I don't know what method was used
> to make the copy, and if anything has been left out during copying. I
> don't have these problems when viewing the live version.
It appears that someone though it a good idea to revoke access for public
to the system tables. You need to see an admin that can address this.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||I am a SQL Server DBA (albeit a rookie) and I had the same problem when
moving a database from one server to another (same SQL level and such).
I raked my brain trying to figure out why my customer could not see
the contents of the database when all indications were that the user
IDs were migrated properly from the old to the new server (did I say
"migrated?" yes, user ids were migrated after generating the ddl using
sp_help_revlogin and making sure that all the permissions for the given
user appear to be identical on both servers).
Then I decided to just delete the user and addd it manually to SQL
Server and ... voila! no more 229 error.
Here is what I wonder (would say figured out but I am not that
confident)... When I migrated the user IDs I did so before I migrated
the database, hoping that I would not get any errors during the
database migration that could have been caused by not having a given
user already defined when an object is being created and/or loaded on
the new server. That must have been the cause of the problem because I
migrated another database without first migrating the user IDs and that
problem did not occur.
Anyone with a better explanation?
Erland Sommarskog wrote:
> Ben Fidge (BenFidge@.discussions.microsoft.com) writes:
> It appears that someone though it a good idea to revoke access for public
> to the system tables. You need to see an admin that can address this.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp