Use STR function.

It's perfect for displaying decimal values and its output is a string.

Mitchell, cursor is not a variable, it cannot be returned as output parameter.

You're trying to use something what exists in other languages but not in SQL.

Explain what you need to...

Conversion of datetime to varchar and back is the worst available option in terms of performance.

Not to mention possible collation problems.

If you find a definition what is "last day of month" you'll get your solution.

Executing of dynamic SQL involves compiling of the SQL.

During compilation SQL Server locks system tables. And does not allow other compilation requests to pass through until the transaction is over.

Because...

santhoshkumar.boregowda (12/2/2008)

---

Thanks Gila,

Actually these types of result are affecting the production in one or other way.

some batches will be having a query like

WHERE col = '0'...

Yep.

Table is just another piece of executable code compiled when CREATE TABLE statement was executed.

If the code is wrong...

Matt Miller (12/1/2008)

---

By all means - coding to validate up front will allow you to get past all of those errors you get from "just throwing it against the way...

My last 2 DB projects are in production one for 2 years, another one...

How many do you expect?

Duplication, not existence, datatype mismatch, what else?

And you need to cover them all any way.

SQL Server works at background, it does not presume interaction with a...

Did you read OP?

I...

Look at you WHERE clause:

WHERE l.List_ID = @list_id

AND CONVERT(int,l.CORP) = c.corp

AND CONVERT(int,l.FRAN_TX_AR) = c.FTA

Here is the answer.

1st, you may safely change datatype for...

Any reason why both indexes on Leads_DST are nonclustered?

Make the index on LIST_ID clustered and you "parameter sniffing" problem will go away.

If you need an answer on your question here it is:

"There is no way".

If you then want to know how to do things properly in SQL read above.

Charindex does not work with text.

It implicitly converts it to CHAR(4000).

If your string to be replaced is after 4000th character it's never gonna find it.

And SQL is a VERY bad...