If you're not monitoring queries through something like extended events, you can't be sure what was called. But, you can check the queries that are currently in cache by hitting...

It's got to be because of the conversion of the dates to strings. Just leave them as dates. Use date math and date comparisons within T-SQL. They work. String manipulation...

I looked through it. I don't see anything egregious. It is doing a lot of work. But you don't have any really obvious issues. At least, none I spotted. I'd...

What makes you think it's Intellisense? That's the type-ahead mechanisms within Management Studio. I haven't heard of, or seen, major blocking issues from that. Instead, blocking is when a query...

I'm with Gail. Probably statistics, but looking at the execution plan would sure help narrow it down.

Wow! Thank you. Very high praise. Happy I can help.

Is it a problem? I mean, you're using a lot of CPU, but are you experiencing slow performance? And further, is that slow performance caused by CPU? What are your...

You can look to the dynamic management function sys.dm_exec_plan_attributes. It will show the user_id that created the plan among other things. You'll just have to pass it the plan_handle.

You can set up extended events to capture logins. That's the one sure way to get it. But if you haven't set that up, I'm not sure there is a...

Default trace and a server-side trace are absolutely one direction for solving this.

But, a better direction would be to take advantage of extended events. They're more lightweight, less intrusive and...

I'm not sure. You may need to open a case with Microsoft. I'd say it sounds like you've set them up on the same ports, but you said you checked...

There isn't a single definition for what exactly is meant by "data dictionary."

Do you mean the table definitions, indexes, constraints, all as defined by T-SQL? Or are we talking about...

IgorMi (12/11/2013)

bugg (12/11/2013)

I have considered this, but it will mean downtime to Enable READ_COMMITTED_SNAPSHOT ON, which unfortunately I cannot do anytime...

Not really. If a user can create a database, they can access that database.

On the existing instance, you can set the user as data_reader only which will prevent them...

It's largely because heap storage goes where ever. It's one of the fundamental issues with heaps and why it's worth pointing out that fundamental storage and access in SQL Server...