for the second time this week, on a SQL 2014 instance, Getting some corruption ; i'm assuming the error is unrepairable/restore from backup .My question is really leaning as to why i might be getting an error; when i look in the Windows Event Log, i see the error below, does that imply i've got a problem with overusing the server, or a problem with physical RAM, maybe, and not the disks themselves? the server is used for DWH/SSAS development, and is a 32 gig of RAM, of which 24 is dedicated to SQL, 4 processor by 2x processor, with 8 virtual cores total.the complete DBCC CheckDB:[quote]DBCC CHECKDB('PyramidDev') WITH NO_INFOMSGS, ALL_ERRORMSGS[color="#FF0000"]Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 47287796087455744 (type Unknown), page (65535:9955320). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -10.Msg 8998, Level 16, State 2, Line 1Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (1:6421872) to (1:6429959). See other errors for cause.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 47287796087455744 (type Unknown), page (65535:9955320). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -10.[/color]CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.CHECKDB found 2 allocation errors and 1 consistency errors in database 'PyramidDev'.[/quote]Event View SQL related Errors:[quote]There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed. [CLIENT: 10.41.10.204]There is insufficient system memory in resource pool 'default' to run this query.[/quote]
↧