Tag Info

Hot answers tagged

8

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 ...


7

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 ...


6

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. ...


3

Even if you configured RBS to use FILESTREAM, TDE does not apply to FILESTREAM: Transparent Data Encryption and FILESTREAM DATA FILESTREAM data is not encrypted even when TDE is enabled.


3

The files are stored in a blob in the sharepoint database and as TDE encrypts all the pages in the database all the files will be encrypted there within. It's important to notice that while the database is mounted on the server the database server will serve the files unencrypted to the Sharepoint application server and it's clients. The Sharepoint ...


3

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 ...


3

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


3

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 ...


2

Try the following: USE db_name_that_you_created; GRANT CREATE TABLE TO db_user_that_needs_to_create_table; GO


2

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.


2

I would suggest double checking all the requirements for enabling FILESTREAM as per: How to: Enable FILESTREAM


2

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.


2

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.


2

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, ...


2

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 ...


2

It is not possible, because you cannot create a backup of an offline database. From MSDN: Without the NO_TRUNCATE option, the database must be in the ONLINE state. If the database is in the SUSPENDED state, you might be able to create a backup by specifying NO_TRUNCATE. But if the database is in the OFFLINE or EMERGENCY state, BACKUP is not ...


2

This is SQL Server updating the statistics on a table. It can be triggered automatically when about 20% of the data in your table changes, or on demand if you run jobs that update statistics. You have a few ways to lessen the pain. You can enable asynchronous statistics updates, which lets SQL Server update stats behind the scenes without blocking other ...


2

I write Minion Backup and this kind of thing would be very easy to do. We allow you to run Pre and Post code before each DB, so for your SharePoint DB, you can just put it into single-user mode and change it back when it's done. However, we can't guarantee that you'll be the one to get that connection. But you can download Minion Backup here and give it a ...


1

SQL does not allow to backup a database when in offline mode. You can also create maintenance plans in order to automate the job. So the first step of you job can be setting the offline databases to online mode and then the maintenance plan will do is work and then the third step will be to set your databases back to online.


1

Two things. First if you are going to do that then make your script this: ALTER DATABASE [TEST_1] SET SINGLE_USER WITH ROLLBACK IMMEDIATE GO USE [TEST_1] GO BACKUP DATABASE [TEST_1] TO DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\test\test_1.bak' WITH NOINIT, STATS = 10 GO ALTER DATABASE [TEST_1] SET MULTI_USER WITH ROLLBACK ...


1

To put it simply - it would work if only one of you were editing the database at a time. If both of you were to edit the database, it could corrupt the file, discard each other changes or cause sync issues. By the way, have you considered Google Docs?


1

Your server has to be a member of the SharePoint farm before it will allow you to install SSRS in integrated mode. Refer to this article for more information.


1

One option is create login with default database option and add role member to login user in database USE [master] GO CREATE LOGIN [CUREMD\NewLogin] FROM WINDOWS WITH DEFAULT_DATABASE=[AdventureWorks] GO USE [AdventureWorks]--- Change DB name to Sharepoint DB Name GO CREATE USER [CUREMD\NewLogin] FOR LOGIN [CUREMD\NewLogin] GO USE [AdventureWorks] --- ...


1

View the default database in user's properties, may be it is master, if so, then change it


1

Verify if your user has permision to connect to database Engine. Right click on Logins -> Properties -> Status. Or grant CONNECT for user. CREATE LOGIN [mydomain\mygroup] FROM WINDOWS; GRANT CONNECT SQL TO [mydomain\mygroup]


1

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 ...


1

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.


1

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.



Only top voted, non community-wiki answers of a minimum length are eligible