Hot answers tagged sharepoint
As this is SharePoint your hands are tied. You can't create indexes or statistics without loosing support from Microsoft. CXPACKET just means that one thread of a parallized query is waiting for another thread to finish waiting for something else. SOS_SCHEDULER_YIELD can mean a few things, typically it means that you need to fix your indexes are you have ...
There is not a lot you can do to tune the database it self. You aren't allowed to create indexes, or statistics. Keep your content databases small. If they get to 100 Gigs you'll want to add another content database (there's ways to do this through the SharePoint UI). As the tables grow you will want to be sure that you are doing index rebuilds and ...
On the face of it, this looks like a classic lookup deadlock. The essential ingredients for this deadlock pattern are: a SELECT query that uses a non-covering nonclustered index with a Key Lookup an INSERT query that modifies the clustered index and then the nonclustered index The SELECT accesses the nonclustered index first, then the clustered index. ...
If this was a classic lookup deadlock, the resource list will include both the Clustered Index and Non-Clustered Index. Typically the SELECT will hold a SHARED lock on the NC index and wait for a SHARED lock on the CI, meanwhile the INSERT will acquire an EXCLUSIVE lock on the CI and wait for an EXCLUSIVE lock on the NC. The resource list in the deadlock xml ...
Restore from your backup if possible. "Allow data loss" is really a terrible option. This excellent article will help you: http://www.sql-server-pro.com/dbcc-checkdb.html
From what I see you created a server login with server roles (DBCreator and SecurityAdmin are server roles). But this doesn't mean it already has privileges on an existing database. What you need to do is to create a user in that database and map it to the login: use your_db create user x for login y exec sp_addrolemember 'db_owner', 'x' This will assign ...
Try the following: USE db_name_that_you_created; GRANT CREATE TABLE TO db_user_that_needs_to_create_table; GO
Is there a SQL event being throw when the snap manager starts the backup? If so there could be an alert setup on that event which is setup to start the job. Check the SQL Agent alerts to see if it is configured to capture anything.
When a maintenance plan is created, a SQL agent job is also created to run the maintenance plan. This way, you can run the job manually or schedule it. If you look inside the steps of the SQL agent job, you will see how the maintenance plan is being called.
I would suggest double checking all the requirements for enabling FILESTREAM as per: How to: Enable FILESTREAM
DBCC CHECKDB uses tempdb and can stress the I/O subsystem heavily when it runs. It uses tempdb to store facts during the checks it is running. Paul explains some of the details of this in his blog post (http://sqlskills.com/BLOGS/PAUL/post/How-does-DBCC-CHECKDB-WITH-ESTIMATEONLY-work.aspx) If you are getting latch contention on the system tables in tempdb, ...
SQL Server gets its time Zone information from the operating system on which it is installed. So if SELECT GETDATE() reveals the right information, then SQL Server is most likely not the problem. You can query the registry on your SQL Server, if you have the appropriate permissions, and see what the server's time zone is set to: DECLARE @TimeZone ...
I do not know much about Sharepoint but in usual cases Oracle client has to be installed into server where application which connects to Oracle is located. So if your application will be running on Application server you should install Oracle client here. Just for the information you can also try Instant Client. It uses less disk space and you do not have to ...
I recently gave a pretty robust explanation on how to handle corruption issues here. Give that a look. I would try dropping / recreating the indexes first, if it does not fix the issue you may have to run the repair_allow_data_loss in your case.
I would be confident you have corruption. Sounds like at least one corrupt data page. What does the contents of msdb.dbo.suspect_pages look like? Refer to http://msdn.microsoft.com/en-us/library/ms191301(v=sql.105).aspx for parsing some of that info.
Unfortunately no, not in SQL Server 2008. According to FILESTREAM Overview - multiple containers can be added to a single FILESTREAM Filegroup but only as of SQL 2012.
Only top voted, non community-wiki answers of a minimum length are eligible