You can't start the service like this. Just grab the service target (the path to the executable sqlservr.exe) and run it in a cmd window...

I have used this in the past with success.

If you're working on a whole folder at a time, you can set the source folder and the target folder using...

Which is usually a bad thing, performance wise.

It means it cannot be evaluated using an index.

This will do the trick

SELECT *

FROM TEST

WHERE CAST(CASE Result WHEN '>5.0' THEN '6.0' ELSE Result END AS float) > 4.0

However, casting will make your predicate non-sargable.

It seems to me the attack aimed at obtaining the database schema definition.

If the application is vulnerable to sql injection, the attacker could have gained access to anything.

Powershell could be the right tool for this job.

See an example here: http://sethusrinivasan.wordpress.com/2012/01/11/powershell-script-to-run-query-against-many-servers-and-send-combined-output-as-email/

Does this happen from the GUI only or from script as well?

Nope.

One server, one license.

Based on what you posted, I suppose that you're not showing us all the code, but just a small portion of it.

Can you share the whole statement, please?

Like2SQL (10/27/2014)

---

(a) We want to move drive C:\ onto the new, better storage but our understanding is that since it installation files, we can't just move the drive. Rather, we...

This should do the trick:

-- merge with output

MERGE INTO @originalTable AS trg

USING @otherTable AS src

ON trg.logicalKey = src.logicalKey

WHEN MATCHED

THEN UPDATE SET trg.datafields = src.datafields ...

Looks like OUTPUT is not an issue here.

For instance, this works:

-- original table

DECLARE @originalTable TABLE (

id int,

logicalKey varchar(50)

)

-- some sample data

INSERT...

Good point, Jeff.

However, building a sophisticated script like Ola's is not something I would recommend to a novice. I would start from something easier.

Try to capture the statements issued by SSMS with Profiler.

Maybe it's a client thing and the parameters supplied by SSMS are wrong.