You have to build the string. Just referencing the parameters won't work.

I'd suggest trying some indexes on the table and using a JOIN to do the UPDATE.

You have parameters that you're passing values to and then those parameters are used in your SELECT statement to return the values passed. That's how parameters work. What you're...

It's a security error that's basically preventing you from making a series of calls to the OS. To run it, you have to do what it's asking for.

This is a VM running on Azure, which means, technically, the HyperV hypervisor although things are a little different...

Fine, but where is it coming from? It's not a part of the query as outlined, so is that thing...

Text plans... blech!

Anyway, like I said, you're getting a scan because of the function:

[SCM].[MEAS_VALUE]<>-1 AND [SCM].[COL3]&239=0

The other two scans are not as obvious. For example, this one:

[M].[COL4]>=0 OR [M].[COL4]=-2.01019e+009

It's...

I'd love to see the execution plans, but this little critter is going to prevent index use:

and ((c.col6 & 0XOEF) =0)

That's going to lead to scans, all the time every...

If you have an account that has access to all the file shares that your backups are going to, you could use that account to run a powershell or batch...

Never heard of it. But my response to one these is always the same, "Cool. Awesome. Can you show me a recovery to a point in time?"

If they can do...

The basic costs break down on the parsing of the query and/or getting the object id of the procedure and then retrieving those from cache by a search on the...

You said variables several times. Be sure to differentiate between variables and parameters. A parameter, defined with the stored procedure or in a parameterized query, can be sampled, or sniffed,...

You can gather information on deadlocks on SQL Server 2008 and better without ever setting a trace flag. Just use the system_health extended event session that is running automatically on...

I'd suggest breaking up your index rebuilds, only do a few at a time in small chunks. And don't swap the recovery model to bulk-logged. If you need to restore...

It all has to do with permissions. I suspect your SQL Server instances are running under local accounts instead of under networked accounts. You'll have issues trying to communicate across...