Viewing 15 posts - 76 through 90 (of 1,132 total)
A Clarification regarding the master database; although the recovery mode can be set to FULL, transaction log backups cannot be performed and transaction log restores cannot be performed.
Here is the...
March 25, 2010 at 1:14 am
Master and Tempdb are always in simple recovery mode and you cannot change the recovery mode.
Model can be any recovery mode where new databases will be in the same mode....
March 24, 2010 at 1:08 pm
The "Backup" command works at the database or database file level and there is no support for table level backups.
There are various utilities available such as the Bulk Copy Program...
March 24, 2010 at 7:09 am
Alter the view and include the "WITH VIEW_METADATA" option. You may also want to also include the "SCHEMABINDING" option, which sometimes improves performance.
From Books On-line:
Specifies that the instance of...
March 21, 2010 at 12:39 pm
Provided that the results support my thoery, will moving each DB to its own instance (on same server) address the problem?
It depend (i hate that answer).
Let us call the...
March 19, 2010 at 8:34 am
My thinking is that the Database B process is simply kicking Database A out of memory. And once Database A gets used for a bit, it's back to where it...
March 19, 2010 at 7:41 am
View INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE may meet your needs.
Returns one row for each column in the current database that has a constraint defined on the column. This information schema view returns information...
March 18, 2010 at 3:43 am
You need to determine which program is having the context switchs by using the process explorer utility and then post the results.
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
March 17, 2010 at 6:51 am
'I got the below warning message for full backup job. " 3/12/2010 12:22:07 AM: Another process might be locking this file The process cannot access the file because it is...
March 14, 2010 at 11:41 am
If you have SQL Mail enabled, then the SQL Server Agent alerts can work.
Set up one alert to any error with a severity of 17 or higher.
Alerts for various performance...
March 13, 2010 at 10:35 am
You can place the backups file anywhere but to refer by drive letter, the drive must within the SQL Server resource group. You can reference using UNCs in the...
March 13, 2010 at 10:24 am
Found this:
SQL Server reports 701: "There is insufficient memory to run this query" when executing large batches
http://support.microsoft.com/kb/2001221
http://support.microsoft.com/kb/2000380
I also recall a SQL Server 2008 "memory leak" condition with linked servers but...
March 12, 2010 at 10:35 am
Saw mister.magoo's post after I had already written a reply, so this may be some duplication.
You should check that:
1) The Distributed Transaction Coordinator is running on both servers.
2) OLE DB...
March 12, 2010 at 7:03 am
MS has added some "Denial of service attacks" protection (SynAttackProtect setting), which can cause this message. See "Troubleshooting: Connection Forcibly Closed" at http://msdn.microsoft.com/en-us/library/ms187005.aspx
Also see "Avoiding TCP/IP Port Exhaustion" at...
March 11, 2010 at 3:16 pm
We've had a few server crashes lately due to memory, so I'm trying to get a real good understanding of how memory works.
With this message?
Error: 701, Severity: 17,...
March 10, 2010 at 2:04 pm
Viewing 15 posts - 76 through 90 (of 1,132 total)