[MS SQL Server] Error in table 'sys.sysbinobjs' on master database |
- Error in table 'sys.sysbinobjs' on master database
- Permissions for add users to one database only
- SSAS - Multiple Instances
- Log Space % increases while size stays the same
| Error in table 'sys.sysbinobjs' on master database Posted: 22 Mar 2011 06:35 AM PDT Hi,We have a SQL server DatabaseIntegrityCheck job to check the SYSTEM_DATABASES, and it shows an error message below in the logs now:Msg 2570, Level 16, State 2, Line 1Page (1:354), slot 28 in object ID 58, index ID 1, partition ID 281474980511744, alloc unit ID 281474980511744 (type "In-row data"). Column "name" value is out of range for data type "nvarchar". Update column to a legal value.CHECKDB found 0 allocation errors and 1 consistency errors in table 'sys.sysbinobjs' (object ID 58).CHECKDB found 0 allocation errors and 1 consistency errors in database 'master'.However, when run the command "DBCC CHECKDB ([master]) ", it returns no error. Don't know what a problem is. Could someone please let me know what we should do? Any fix need to be done?Thanks in advance,Marie |
| Permissions for add users to one database only Posted: 12 Aug 2013 05:28 AM PDT Is there a way that I can set a SQL account to be able to add new users to only a certain database and no other databases? |
| Posted: 13 Aug 2013 01:47 AM PDT sorry for my ignorant question: Is it possible to install multiple SSAS instances in a clustered/nonclustered environment with the same IP address with different port numbers. |
| Log Space % increases while size stays the same Posted: 12 Aug 2013 12:10 PM PDT We are using Microsoft's System Center to monitor everything. One of the issues I am having with maintaining our DBs is the reports that run against fail after a few days when the log space percentage comes close to 100% (usually at about 98% is when they start to fail). The log file is set to 15,000 MB, but the size of the log is only about 350 MB. The only way I can get the reports running again is to set the database to backup the DB and transaction logs, set the DB to simple, truncate the log file, set the DB back to full and cross my fingers. Can anybody think of any reason why the this would be occurring? I can upload the set of reports on the logs' size and percentage if that will help clarify things. If you have any other questions in relation to this, please feel free to ask.Thank you for all of your help. |
| 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