Yup. That's one of the key selling points for it. Backed up with the database, transactional and will triggers, but in the file system, not split up in database pages

2 very big databases both used by 1 app. Very heavy temp table usage.

All 12 processors used by SQL. 64bit Itanium Enterprise edition on Server 2003 Datacenter. It was SQL...

It should work.

What more do you want?

With stored procs/parameterised queries is the only way to be sure. Yes, it's a lot of work. how much work is going in to fixing that database?

If you're just replacing...

Other option is to enable traceflag 1204 or 1222. SQL will write the deadlock graph into the error log.

Pleasure.

It's simply a data type and conversion issue. Any expression that just involves integers will return an integer. If the expression inlcludes multiple types, then the result will be of...

Providing you set the number to 1 for the rows that you want returning. In the sample you gave, code 3x doesn't have a 1.

There's no such thing as a physical order based search in SQL server. A table is, by definition, an unordered set.

If you don't have a column specifying the order,...

Cast one or both to float/numeric before doing the divide

(CAST(@used AS FLOAT)/ CAST(@max AS FLOAT))*100

Use float is you're not worried about floating point inaccuracies, otherwise use a numeric with the...

Link doesn't want to show. Please convert the image to jpg and attach it to a post here. Is much easier.

set @ber = 6/5 is doing an integer divide, hence throwing away the fraction. Try the following

set @ber = 6.0/5.0

Then you're asking for SQL injection.

If I may suggest...

Look into moving code into stored procs and calling with parameters. It's a far more secure way of doing things.

How are...

It's an option, though the encryption is trivial to undo. There are a number of utils available on the web to decrypt 2000 or 2005 stored proc encryption.

There's no real...

Are you sure that every possible place that input is entered (including query strings) is checked for injection?

Are you building up SQL statements and executing them or are you using...

I would recommend a clustered index on that table. Without knowing what other queries run and how the data's distributed, I can't recommend what column to put it on.