Paul,
I recently 'inherited' the EIS database. It looks like the index on table 'PREMIUM_FACT_TABLE' is corrupted. I cannot drop the index. Here is the result from DBCC CHECKDATABASE:
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -674037686, index ID 256, page ID (1:201566). The PageId in the page header = (3:324935494).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -674037686, index ID 256, page ID (1:201567). The PageId in the page header = (3:325001030).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -674037686, index ID 256, page ID (1:203870). The PageId in the page header = (3:475930446).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -674037686, index ID 256, page ID (1:203871). The PageId in the page header = (3:475995974).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 775673811, index ID 0: Page (1:201565) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 775673811, index ID 0, page (1:201565). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 775673811, index ID 0: Page (1:201566) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 775673811, index ID 0: Page (1:201567) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 775673811, index ID 0: Page (1:203869) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 775673811, index ID 0, page (1:203869). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
CHECKDB found 0 allocation errors and 4 consistency errors in table '(Object ID -674037686)' (object ID -674037686).
DBCC results for 'EIS'.
DBCC results for 'sysobjects'.
There are 67 rows in 2 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 73 rows in 7 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 691 rows in 52 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 127 rows in 16 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 20 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 15 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 309 rows in 2 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'AGTMASTR'.
There are 4372 rows in 398 pages for object 'AGTMASTR'.
DBCC results for 'STATECD'.
There are 67 rows in 1 pages for object 'STATECD'.
DBCC results for 'MKTGREP'.
There are 14 rows in 1 pages for object 'MKTGREP'.
DBCC results for 'STACCPRD'.
There are 168 rows in 1 pages for object 'STACCPRD'.
DBCC results for 'EISTABLE_VK'.
There are 9 rows in 2 pages for object 'EISTABLE_VK'.
DBCC results for 'COVERAGE'.
There are 586 rows in 9 pages for object 'COVERAGE'.
DBCC results for 'YEARMNTH'.
There are 48 rows in 1 pages for object 'YEARMNTH'.
DBCC results for 'PremTest1'.
There are 0 rows in 0 pages for object 'PremTest1'.
DBCC results for 'PREMIUM_FACT_TABLE'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 775673811, index ID 0: Page (1:203870) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 775673811, index ID 0: Page (1:203871) could not be processed. See other errors for details.
There are 9853114 rows in 131244 pages for object 'PREMIUM_FACT_TABLE'.
CHECKDB found 0 allocation errors and 8 consistency errors in table 'PREMIUM_FACT_TABLE' (object ID 775673811).
DBCC results for 'CLAIMS_FACT_TABLE'.
There are 1308975 rows in 26180 pages for object 'CLAIMS_FACT_TABLE'.
DBCC results for 'RATESET'.
There are 142 rows in 1 pages for object 'RATESET'.
DBCC results for 'EIS_SQL_STATEMENTS'.
There are 1 rows in 1 pages for object 'EIS_SQL_STATEMENTS'.
DBCC results for 'dtproperties'.
There are 0 rows in 0 pages for object 'dtproperties'.
DBCC results for 'JOBSTATUS'.
There are 2 rows in 1 pages for object 'JOBSTATUS'.
CHECKDB found 0 allocation errors and 12 consistency errors in database 'EIS'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (EIS ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
The command DBCC DBREINDEX (Premium_fact_table); returns:
Server: Msg 823, Level 24, State 2, Line 1
I/O error (torn page) detected during read at offset 0x000000626ba000 in file 'E:MSSQLDATAEIS.mdf'.
I ran into a few consistency problems this morning that I found after receiving a torn page error on our SQL 2000 box (SP4). Here’s the error messages I get from running DBCC CHECKDB WITH NO_INFOMSGS, ALL_ERRORMSGS :
Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 379493089280 owned by data record identified by RID = (1:647611:14) PK1 = 1300583. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 379544338432 owned by data record identified by RID = (1:648136:32) PK1 = 1300903. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 379567996928 owned by data record identified by RID = (1:648142:19) PK1 = 1301226. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 379587067904 owned by data record identified by RID = (1:648474:43) PK1 = 1301482. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407334912 owned by data record identified by RID = (1:1387313:46) PK1 = 3277593. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407400448 owned by data record identified by RID = (1:1387313:47) PK1 = 3277594. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407465984 owned by data record identified by RID = (1:1387313:48) PK1 = 3277595. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407531520 owned by data record identified by RID = (1:1387313:49) PK1 = 3277596. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407597056 owned by data record identified by RID = (1:1387313:50) PK1 = 3277597. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407662592 owned by data record identified by RID = (1:1387313:51) PK1 = 3277598. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407728128 owned by data record identified by RID = (1:1387313:52) PK1 = 3277599. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407793664 owned by data record identified by RID = (1:1387313:53) PK1 = 3277600. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 1979154096: Errors found in text ID 552407859200 owned by data record identified by RID = (1:1387313:54) PK1 = 3277601. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558591), slot 8, text ID 552407334912 is not referenced. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 1979154096, index ID 255: Page (1:558593) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 1979154096, index ID 255, page (1:558593). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 0, text ID 552407334912 is referenced by page (1:1387313), slot 46, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 2, text ID 552407400448 is referenced by page (1:1387313), slot 47, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 4, text ID 552407465984 is referenced by page (1:1387313), slot 48, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 6, text ID 552407531520 is referenced by page (1:1387313), slot 49, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 8, text ID 552407597056 is referenced by page (1:1387313), slot 50, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 9, text ID 379493089280 is referenced by page (1:647611), slot 14, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 10, text ID 379544338432 is referenced by page (1:648136), slot 32, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 11, text ID 379567996928 is referenced by page (1:648142), slot 19, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 12, text ID 379587067904 is referenced by page (1:648474), slot 43, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 14, text ID 552407662592 is referenced by page (1:1387313), slot 51, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 16, text ID 552407728128 is referenced by page (1:1387313), slot 52, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 18, text ID 552407793664 is referenced by page (1:1387313), slot 53, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 20, text ID 552407859200 is referenced by page (1:1387313), slot 54, but was not seen in the scan. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:647791), slot 6, text ID 379493089280 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:648120), slot 7, text ID 379544338432 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:648356), slot 6, text ID 379567996928 is not referenced. Server: Msg 8964, Level 16, State 1, Line 1 Table error: Object ID 1979154096. The text, ntext, or image node at page (1:648497), slot 7, text ID 379587067904 is not referenced. CHECKDB found 0 allocation errors and 33 consistency errors in table 'QTI_RESULT_DATA' (object ID 1979154096). CHECKDB found 0 allocation errors and 33 consistency errors in database 'bb_bb60'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (bb_bb60 ).
After looking through similar posts here in the forum, I also ran a checktable on the sysindexes, sysobjects, syscolumns, and systypes tables, since they seem to be popular sources of errors. However, no error messages were reported. They seem to be all related to the one table referenced by the CHECKDB statement.
Is this something that is repairable, or will it require a restore? Thanks for the help!
ren writes "the error first appeared in error log as
I/O error (bad page ID) detected during read at offset 0x0000007852a000 in file 'I:RD1DATA7RD1DATA7.ndf'..
DBCC checkdb return message
Database 'dbname' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECKDB processing.
dbcc checktable ('syscolumns') returned
Server: Msg 8928, Level 16, State 1, Line 1 Object ID 3, index ID 0: Page (10:621247) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 1185438913, index ID 0, page (10:621247). Test (!(m_flagBits & PG_ALIGNED4)) failed. Values are 16386 and 1185438913. Server: Msg 8940, Level 16, State 1, Line 1 Table error: Object ID 1185438913, index ID 0, page (10:621247). Test (IsAligned (m_freeData)) failed. Address 0x2ad is not aligned. DBCC results for 'syscolumns'. There are 11744838 rows in 188015 pages for object 'syscolumns'. CHECKTABLE found 0 allocation errors and 1 consistency errors in table 'syscolumns' (object ID 3). CHECKTABLE found 0 allocation errors and 2 consistency errors in table '(Object ID 1185438913)' (object ID 1185438913). repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (RD1.dbo.syscolumns ).
Since the repair option requires single user mode, it will have big impact on the user. Is the I/O error (bad page ID) on the file a hardware failure? If not, what would cause this problem.
I recently updated the datatype of a sproc parameter from bit to tinyint. When I executed the sproc with the updated parameters the sproc appeared to succeed and returned "1 row(s) affected" in the console. However, the update triggered by the sproc did not actually work.
The table column was a bit which only allows 0 or 1 and the sproc was passing a value of 2 so the table was rejecting this value. However, the sproc did not return an error and appeared to return success. So is there a way to configure the database or sproc to return an error message when this type of error occurs?
I have a parent package that calls child packages inside a For Each container. When I debug/run the parent package (from VS), I get the following error message: Warning: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
It appears to be failing while executing the child package. However, the logs (via the "progress" tab) for both the parent package and the child package show no errors other than the one listed above (and that shows in the parent package log). The child package appears to validate completely without error (all components are green and no error messages in the log). I turned on SSIS logging to a text file and see nothing in there either.
If I bump up the MaximumErrorCount in the parent package and in the Execute Package Task that calls the child package to 4 (to go one above the error count indicated in the message above), the whole thing executes sucessfully. I don't want to leave the Max Error Count set like this. Is there something I am missing? For example are there errors that do not get logged by default? I get some warnings, do a certain number of warnings equal an error?
Starwin writes "when i execute DBCC CHECKDB, DBCC CHECKCATALOG I reveived the following error. how to solve it?
Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -2093955965, index ID 711, page ID (3:2530). The PageId in the page header = (34443:343146507). . . . . . . . .
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1635188736)' (object ID -1635188736). CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1600811521)' (object ID -1600811521).
. . . . . . . .
Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -8748568, index ID 50307, page ID (3:2497). The PageId in the page header = (26707:762626875). Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -7615284, index ID 35836, page ID (3:2534). The PageId in the page heade"
I have been receiving 644 errors on an index for one of my tables. We have dropped and rebuilt the index. Even BCP out, drop the table, create the table and BCP in everything and still have problems.
Has anyone else experienced problems with 644 errors? Did you ever determine the cause and are they any preventative ideas?
Ok, whenever I try to connect, I get the following Error messages:
"SQL Server Registration failed because of the connection failure displayed below. SQL Server does not exist or access denied. ConnectionOpen (Connect())"
"An Error 1069 occured while performing this service operation on the MSSQLServer Service"
I even went as far as uninstalling and reinstalling, but to no avail. Does anyone have an idea what's causing this? It was working fine and then all the sudden one day I start getting these messages and it won't work.
I have a dynamics db that is used for archival purposes and it is not used very often. Now that someone decided to get some info out of it it wont let them. when I run dbcc I get the following message:
Msg 5242, Level 16, State 1, Line 1 An inconsistency was detected during an internal operation in database 'PACIF'(ID:12) on page (1:19451). Please contact technical support. Reference number 6. Msg 8921, Level 16, State 1, Line 1 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
I was just wondering if this meant anything to any of you? and since all of my backtapes have the same issue, is there any way to fix it?
Running SQL 05 Standard on a Vista box and I have about had it with Vista. Anytime I try to launch Config Manager I get Cannot connect to WMI provider. You do not have permission or the server is unreachable. So try I googled and tried everything I can fine from http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx
C:Program FilesMicrosoft SQL Server90Shared>mofcomp "C:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof" and now I get ..
An error occurred while processing item 10 defined on lines 73 - 79 in file C:s
qlmgmproviderxpsp2up.mof:
Error Number: 0x80041003, Facility: WMI
Description: Access denied
Compiler returned error 0x80041001
so I try every possible different permission setting for anything sql server - problem still happening... try procmonitor.. find the registry keys and grant full contorl to all of them.. problem still happending.. run the little fixwmi.cmd I found.. problem still happening..
try to uninstall SQL Server.. NOT - WMI error - try to reinstall over--- NOT WMI error.
What do I need to do to get this working. .this is becoming a serious hinderance to my productivity!!!
what a want to know is if there s a way to log sql server errors on a log file, table, these errors are not sql server logs which already exists, i want to log dead locks, sql server timeout errors vs on sql server or somewhere.
Hi Expert, I have a datagrid which is filtering by a dropdownlist and a search textbox.
The dropdownlist allows to select the column they want to search. The search textbox allows to enter the item they want based on the selection from dropdown. Now I use a StoreProcedure to select the data they need, so I pass-in @DropDownListValue int and some others parameters, such as @ID int, @OrderType varchar(50) ... When I search for ID = 163 Input string was not in a correct format. Then when I check with the SQL Server Profiler, I found out that: exec usp_SelectOrder@DropDownListValue=N'1',@ID=N'163',@OrderType=N'163',@OrderSeries=N'163' ... I already set every parameter's default value to NULL. How can I solve for this? Thanks!!
Why on earth is this not working, It WILL insert if there are NO apostheres (" ' "), but if I say like, "Cedric's Group" It will error out. I thought this approach was suppose to handle this character? Thanks for any insight, String sqlStr = "Insert into cardgroups (username,groupname,insertdt,groupid) values (@username,@groupname,@insertdt,@groupid)";
Imports System.Data.SqlClientImports System.DataImports Microsoft.SqlServerPartial Class _Default Inherits System.Web.UI.Page Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click End Sub Protected Sub TextBox3_TextChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles TextBox3.TextChanged End Sub Protected Sub SqlDataSource1_Selecting(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.SqlDataSourceSelectingEventArgs) Handles SqlDataSource1.Selecting End Sub Protected Sub Save_Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Save_Button1.Click Dim conn As New SqlConnection() conn.ConnectionString = Data Source=REDSTONE;Persist Security Info=True;User ID=******;Password=******;Unicode=True End SubEnd Class
End of statement expected. C:Documents and SettingskasireddyMy DocumentsVisual Studio 2005WebSitesBankCustomerInfo.aspx.vb 'System.Data' is a namespace and cannot be used as an expression. C:Documents and SettingskasireddyMy DocumentsVisual Studio 2005WebSitesBankCustomerInfo.aspx.vb C:Documents and SettingskasireddyMy DocumentsVisual Studio 2005WebSitesBankCustomerInfo.aspx.vb
Hello to all, On my webPage I have Used one SQLDataSource to access DataBase. Now whenever some error occures it shows error page by default. I am not able to catch Errors and tackle in my way... Furthermore in this new structure of accessing DataBase even I do not know where to write Try... Catch...
Well there's always a first for everything!! I have a SQL 7.0 server on sP1 and ran upgrade to sp3 and recieved error 'error in upgrade script' retry or cancel. When I retried the upgrade ended. I tried to run the upgrade again and it tries continue where it ended before, but the upgrade ends unsucessfully. I even tried extracted the sp3 exe to a diffrent folder and ran the sp3 upgrade with same results.
I started the MSSQL service ok but not able to use Query Analyzer, DTS, EM.
Get the following message:ISQL.EXE - Entry Point not found. The procedure entry point?DeleteRow@CDataCTLStorage@@UAEJJPAPAG@Z could not be located in the dynamic link library SQLGUI.dll
I get similar msgs when trying to open DTS, Enterprise manager from the server. The user databases and appear to be ok. I am able to get to Query Analyzer, etc. from my worksation fine.
Has anyone encountered this before? Is there a fix for it or do I need to rebuild the server from SP1 and restore the databases, etc.??
It gives following errors 1.time out 2.general network failure
* Are these due to large number of online connnections *If so what is the maximum number of connections possible *what is the hardware requirement to avoid this *what is the impact on stored procedures *How to tune the server to overcome the problems *I'm currently using the standard edition what is the impact on enterprise edition
Over the last few weeks we've been having problems with a particular table in our live OLTP database - dbcc checkdb has been reporting consistency errors.
Initially i took the db offline and fixed the errors using checkdb and replacing the deleted records from a backup of the table. After some investigation it appeared that the errors were being caused when the unique clustered index on the table was rebuilt during weekend maintenance. After a lot of testing i was sure this was the case - so i just deleted the index (the table is small and was over-indexed anyway) and the errors stopped occurring. I didn't understand why the errors had occurred in the first place, and i wasn't convinced that the index was the real problem, but the errors had gone - so that was ok for the short term.
A few things still bugged me:
1. For audit purposes we maintain a copy of the table in question (populated via triggers on the live table) and this showed up consistency errors too. This led me to suspect the problem was with the data itself or the structure of the table - unfortunately there's nothing remarkable about this small, rarely updated table at all (apart from the fact that it's vital for our business!).
2. Any database built from backups of the live db consistently report errors now despite the fact that the backups were made after the problem was resolved and when dbcc checkdb reported NO errors (I maintain a number of test and olap databases in this way). What's happening here? (My guess is that the backup and restore process involves rebuilding indexes, rearranging data, etc. and this is resurrecting the problem) I couldn't help feeling that despite having apparently fixed the errors they were still lurking out there somewhere....
3. At no point did the data in the table appear to be corrupt in any way from the user perspective. This provokes two questions - is dbcc checkdb reliable at both reporting and fixing errors, and how serious are consistency errors?
After removing the suspect index everything was fine for a few weeks until this morning - when errors were again reported on the same table. After hours spent testing and playing around with this (dropping indexes, dropping or truncating the table and re-populating from ascii files, etc.) i've now hit a brick wall. I still suspect the problem is related to the data itself or the structure of the table but can't get any further.....so..
Has anyone come up against a similar problem? Any suggestions for the next course of action? Can anyone point me to documentation on checkdb or consistency errors (other than what's in BOL or the MS knowledge base)?
I am getting the error: The Procedure entry point snmpsvcgetenterpriseoid could not be located in the dynamic link library snmpapi.dll at start up of my nt4 sql server box. The only thought to that is that I need to reinstall SNMP. But I cant find the SNMP Agent anyware for me to reinstall. If you have ever seen this and have a better idea of how to fix it or if you know were i can find the agent it would be gretly apreciated.
I have tried to make a DTS task running a batc-file on the same server as the SQL program is running using the CmdExec command.
My Command is as follows:
CmdExec serverpathatchname.bat
The problem is that everytime the step runs it report the following error:
"The system cannot find the file specified."
In the bat file I am also trying the de-map/map a network drive with another loginname/password than the one used on the SQL-server -> is this i problem?
Hope to hear from you soon, this is a bit urgent!!
Please provide tips to this adresse: qtip@bigfoot.com
I'm running SQL 7.0 with SP2 applied. I have a database that I'm trying to replicate over the Internet.
I'm having a problem getting the initial snapshot. The total amount of data in the snapshot is 3GB. One .bcp file is 2GB and another is roughly 900MB. There are also a few smaller files.
I have my publisher and distributor setup correctly as well as my subscription. I have tested with smaller datasets. Near as I can tell, there is a problem with my files being too big. I get all the .sch files. The first .bcp file is the 2GB file.
I have tried replicating to another server on my LAN (100base-T) and get the same error.
I don't have the exact error, but it's something like: 'Failed to get file sql01_data1_data120000601105138igfile.bcp'
In my FTP Log, I see that transfer was started then aborted.
Any help on how to deliver large amounts of data over FTP would be greatly appreciated.
I have the following severity errors 19-25. I am a new using to SQL Server 7.0 and would like some advice in dealing with these errors. I am going to run the DBCC CHECKDB to determine what the errors are. Is this the right approach. Thanks!!!
I thought this SP would return 547(foreign key constraint voilation) when column 'thing' was being referenced in another table. Instead, when the front-end application code calls this SP it gets a 1 from the delete statement itself. In other words, my return statement never seems to get executed. Is there any way of achieving this? In other words, I want to trap the error 547 and return that to the front-end.
Hi! Has anyone run into this error?... In SQL 7 EM, I right-click on Users under a particular database, select New Database User and get the following error: Error 16916: A cursor with the name 'hCForEachLogin' does not exist. The only way to add a database user is to modify the Login for access to that database. This is fine with me, but some of our clients do not have privileges to administer server logins, only the database logins.
Also get a similar message when I right-click a table and select Properties: Error 16916: A cursor with the name 'hC' does not exist. In this case, when I click OK, I do get the Properties dialog box.
We did not notice this error before applying SP1, so it may be related to that. I welcome any ideas or comments. Thanks!
We have recently upsized several Access databases to SQL 7.0. I created the ODBC datasource to an Access frontend. The tables open but I get the following error when I try to update any of the tables:
ODBC update on a linked table "tablename" failed.
Followed by:
[Microsoft][ODBC SQL Server Driver][SQL Server]The text, ntext and image data types cannot be used in the WHERE, HAVING, or ON clause except with the LIKE or IS NULL predicates [#306].
I had to reboot a server today due to the fact that it was not responding. I found the following error messages in the log. I was able to look up the errors in books on line and found that the database was not corrupt but encountered some type of error took place and locked everything up. Is there a way that I can research these errors further to determine what caused them? Has anyone had experience with this before? Any help would be appreciated? - Thanks
Error : 915, Severity: 21, State: 1 Descriptor for system catalog 'ADMINISTRATOR' not found in DBTABLE chain for database 'firstar' - all system catalogs should reside permanently in this chain. Error : 617, Severity: 21, State: 1 spid23 Descriptor for object '156579646' in database '8' not found in the hash table during attempt to unhash it.
I am having this problem with using a linked server to another dB. I can read tables from the server, but cannot update the same tables (permissions are ok). I get the message
The requested operation could not be performed because the OLE DB provider 'MSDASQL' does not support the required transaction interface
Does anyone have an idea where I should start looking? What interface are they talking about? I am linking with a system DSN running the Connx 8.3 driver.
Question: Is there a way to change the threshold for the number of errors encountered by bcp before it quits? I've looked in BOL and on-line and didn't find anything.
Background: I'm using bcp to populate tables from files residing on the NTFS. This process is an upgrade from 6.5. The problem is that after 10 errors are encountered, the BCP quits but I have many more rows to load from the file. In the past, this wasn't an issue.
