Viewing 15 posts - 12,481 through 12,495 (of 49,557 total)
Resource governor (though it may not do what you expect) and server memory settings.
July 4, 2013 at 6:20 am
SQL will never automatically change the recovery model. If it was changed, someone changed it.
Check the default trace, if the change was recent enough it may still be in there.
July 4, 2013 at 4:04 am
SQLSACT (7/4/2013)
if you are changing the Clustering key at all with your updates, all nonclustered indexes will be affected as well...
July 4, 2013 at 3:59 am
There are no settings or switches that allow you to directly control the plan cache size. It's maximum will be a function of the max server memory, that's about all.
July 3, 2013 at 11:46 am
Not a good idea.
Snapshots impact insert/update/delete performance, they take up space, they can't be backed up and if for any reason you need to restore the source database you'll have...
July 3, 2013 at 9:08 am
Check that the database owner is set to a valid account. SA is often used.
July 3, 2013 at 9:01 am
If you are never modifying any of the columns that are in the index, then the index has no update overhead. It'll still add overhead to inserts and deletes, but...
July 3, 2013 at 9:00 am
Don't create missing indexes off the missing index DMV unless you've tested and ensured they really are useful.
July 3, 2013 at 1:27 am
That doesn't fail because of something called deferred compile. If a table isn't found at parse/compile time, the statement that refers to that table is not parsed or compiled (past...
July 3, 2013 at 1:13 am
When your database is damaged and you are trying to do a last-ditch backup of the log before starting restoring over it, or when for other reasons you're restoring or...
July 3, 2013 at 1:08 am
Viewing 15 posts - 12,481 through 12,495 (of 49,557 total)