Wow .. Can't get the idea of the question **at all** !!

That's much better (consistent) and does not requires of any tricks!

That "feature" can only be controlled with SET ANSI_WARNINGS OFF which is a connection property. You could try BULK INSERT instead and run it with that SET option "off". I...

make them part of SQLAgentReaderRole

rruest (1/7/2009)

---

I have a few SELECTS joined by UNION ALL... pseudo code:

SELECT somedata FROM Table1

UNION ALL

SELECT somedata FROM Table2

The query works perfectly. The user requires me to limit the...

compression works at the "table" level why would you care to move it out of the database?

Don't forget to post back with the results ... 😉

Although the article is well written but I have a word of advice. For very large tables row_number() over().. has been inefficient for me when it comes to pagination!

GSquared (1/6/2009)

---

Just had another thought. You could accomplish much the same thing as the complex join statement by using an Except query between inserted and deleted and then joining...

By the way if the columns are "nullable" you need three way comparison like:

(

i.col1 <> d.col1

or (i.col1 is null and d.col1 is not null)

or (i.col1 is not null and d.col1...

I have witnessed the quality of your answers. I know it was just a glitch 😀

I am glad you got it!

In addition your trigger should only perform the update IF the columns on the "deleted" and "inserted" tables have different values. That way you will be minimizing the impact of...

How about ?

;WITH cte

AS

(

SELECT a.application_id,

d.brandname,

dd.dosage,

t.renew,

...

I think that Grant forgot one link

UPDATE TABLE

SET str_val = x.str_val

FROM TABLE x

WHERE x.prop_id = 131

and TABLE.prop_id = 130

and TABLE.tocid = x.tocid