Check the default trace, DDL changes are logged in there.

The system tables won't help you, sys.indexes does not have a create_date column

No way to answer such a general question. Procedures calling procedures however doesn't cause bad performance. Badly written code and poor indexing causes poor performance. You either need to do...

1) Don't use Task Manager to check SQL Server's memory, it can be wrong

2) SSMS is not the SQL Server engine. It's SQL Server Management Studio. It shouldn't be getting...

You've either got a filter in the trace definition or the deadlock didn't occur.

andy 61637 (10/1/2015)

---

Is there a way to have SSMS generate a create script using ; instead of go ? My create script is huge, quite a lot of editing...

So, um, whereabouts in...

Please post the table and index definitions and the actual execution plan, saved as a .sqlplan file. A picture of the query plan is not very useful.

Lock resource hash value. SQL uses a hash function on the index keys for locking purposes.

It's not all that useful, unless you want to use the %%lockres%% function to...

GO is not a T-SQL command. It's an indicator for Management Studio as to where the batches of commands end. Hence it'll cause errors in anything other than Management Studio

SELECT * FROM sys.procedures

It's not going to tell you what was changed, or by who, just when the procedure was created and modified. The what and the who you get...

http://sqlinthewild.co.za/index.php/2010/09/14/one-wide-index-or-multiple-narrow-indexes/

>1.

The cardinality estimates don't imply whether or not you need an index. They just tell you about estimation errors. What tells you that you probably need an index here is...

It's a correlated subquery. The fact that the outer query is an update doesn't change that, it's a subquery which references a table in the outer query, that's a correlated...

I understood you just fine. The only restore which a snapshot can be used for is to revert (restore) the source database to the time which the snapshot was created.

A...

No.

That command removes all clean data pages from the cache immediately. If your slowdown was caused by the overhead of loading data from disk, then the next execution will...