[MS SQL Server] Memory assigned to the OS |
- Memory assigned to the OS
- Monitoring a remote SQL Server
- Cannot generate SSPI context
- DBCC CHECKTABLE not reporting errors
Posted: 26 Sep 2013 09:46 AM PDT Total physical RAM on the system is 288GB.Min and Max memory assigned to SQL Server is 0 and 280GB.Should I assume that 8GB is assigned to the OS? Is there a way to verify the amount of memory assigned to the OS? |
Monitoring a remote SQL Server Posted: 27 Sep 2013 01:29 AM PDT Can dbWarden be installed on a nonproduction SQL Server and be used to monitor a production server? I installed dbWarden in our test environment and really like what dbWarden has to offer, but I was wondering if there was a way to point the same installation to monitor our production environment as well. Thank You, Rob |
Posted: 26 Sep 2013 12:03 PM PDT Friends,I want to know how can I fix it problem... "Cannot generate SSPI context". It happened when I was connected via Windows Authentication using account active directory (exclusive for engine sql server), and this account have permission Administrator in database server. If a put Local system (engine sql server - configuration manager), success via windows authentication, but using this account that I created, have a problem: Cannot generate SSPI context. someone help me?Thanks! |
DBCC CHECKTABLE not reporting errors Posted: 26 Sep 2013 07:51 PM PDT Hi,I've recently implemented a new DBCC INTEGRITY check process running a combination of CHECKDB (for the smaller databases) and CHECKTABLE for larger - spread over a few days. During my testing of the CHECKTABLE element, I've noticed that the CHECKTABLE does not always report the integrity errors. :w00t:If I repeatably run the check, about 1 in 4 times it reports no errors at all, the other times it does - see below :-ERRORS :-Error Level State MessageText8928 16 1 Object ID 2105058535, index ID 0, partition ID 72057594038779904, alloc unit ID 72057594039828480 (type In-row data): Page (1:79) could not be processed. See other errors for details.8939 16 98 Table error: Object ID 2105058535, index ID 0, partition ID 72057594038779904, alloc unit ID 72057594039828480 (type In-row data), page (1:79). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.2593 10 1 There are 911 rows in 11 pages for object "CorruptTable".8990 10 1 CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'CorruptTable' (object ID 2105058535).No ERRORS :-Error Level State MessageText2593 10 1 There are 911 rows in 11 pages for object "CorruptTable".I should add, for the test, I manually corrupted the "test" database by manually editing the MDF files on a particular value. This issue is occuring on SQL2008(SP2), on my SQL2012 instance it seems to behave itself as expected. I appreciate that this could because this is a forced corruption, but surely a currupt database is still a corrupt database by whatever means.Has anyone else seen this behavour?Thanks. |
You are subscribed to email updates from SQLServerCentral / SQL Server 2008 / SQL Server 2008 Administration To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |
No comments:
Post a Comment