Alexander Suprun (6/12/2013)

---

The smaller picture doesn't mean that the plan is better. Learn to read execution plans if you want to understand what's really going on. The scalars cost nothing....

I will have to wait until the issue happens again to get the actual execution plans. I...

Luis Cazares (6/11/2013)

---

But I'm using a wildcard as the leading character and it won't allow SQL Server to use an index.

if the leading character in a LIKE clause is a...

Just to clarify, but that query is SARGable and could use an index.

http://www.sql-server-performance.com/2007/t-sql-where/2/

If you use a leading character in your LIKE clause, then the Query Optimizer has the...

Jeff Moden (6/6/2013)

---

NEVER EVER grant sysadmin privs to a user or application login. It may take a bit to find the right way to do this but granting sysadmin to...

It's helpful if you get an "unexpected result", that you post what the result is. I expect what you actually got was an error about the ambigious column "month", so...

Does this do what you are looking for?

SELECT C_NAME, ROW_NUMBER() OVER(PARTITION BY C_NAME ORDER BY C_NAME ASC) AS ITEM_NO, REQ_ITEM FROM @test1

Does the following do what you're looking for?

SELECT name, LOGINPROPERTY(name, 'DaysUntilExpiration') AS DaysUntilExpiration

FROM sys.sql_logins

WHERE LOGINPROPERTY(name, 'DaysUntilExpiration') <= 30

The link describes what you do, but you end up creating a scheduled task in Windows that will call the "sqlcmd" executable with a parameter that will execute the stored...

Did you see this link? http://support.microsoft.com/kb/2019698

The text for the sp_statement_starting event specifically says "Occurs when a statement inside a stored procedure has started.", so I do believe it is counting the SQL statements inside your...

In our case, I queried the ExecutionLog table in the SSRS database and we have 0 records that have a status other than rsSuccess. They don't run many SSRS reports...

Coincidentally, we have this exact same problem with one of our servers. We are running MS CRM v4.0 and the SQL server it exists on has this problem maybe once...