If you want just the company name returned, this should (will?) be more efficient:

SELECT [Company Name]

FROM dbo.CompanyInfo --#CompanyInfo

GROUP BY

[Company Name]

HAVING

MAX(CASE WHEN [Transaction...

Be sure to add a:

SET NOCOUNT ON

to the start of the trigger:

CREATE TRIGGER ... ON ... AFTER|INSTEAD OF ...

AS

SET NOCOUNT ON

...

And for a very minor efficiency gain you should add...

Michael Valentine Jones (1/29/2014)

---

Debora (1/28/2014)

---

Getting "The conversion of a varchar data type to a datetime data type resulted in an out-of-range value." error when running the below script:-

delete from table

WHERE...

Luis Cazares (1/28/2014)

---

ScottPletcher (1/28/2014)

---

Don't convert to a datetime, just compare it as characters. Invalid data may still get through, but you can't easily at all correct invalid data on...

Don't convert to a datetime, just compare it as characters. Invalid data may still get through, but you can't easily at all correct invalid data on the fly in...

Define the index based on how you will query it, and the cardinality of the keys.

If you will always specify the second column in the conditions for the...

I think you can move the master db the same way for a cluster as you would for a stand-alone instance. Use the "SQL Server Configuration Manager" to put...

For uniqueness across servers, you can also use a second value, which can often be just a smallint, that identifies the original server that assigned the id. That way,...

You'll want indexes on the lookup guids. And, since they're guids, you'll need to rebuild the indexes fairly frequently. You should also strongly consider reducing the FILLFACTOR on...

If you can use online rebuild, it might be worth cancelling the current index create and running an online version.

Also, you should consider specifying other options -- or not --...

TheGreenShepherd (4/12/2012)

AddressParseStatus is nchar(1) and is used to indicate the value returned by our USPS validation software. It has pretty low cardinality, only 9 possible values. There are roughly 1B...

Actually the SELECT ... INTO is more efficient if the statement can be minimally logged.

I did a search in Books Online for something to verify that:

"

With minimal logging, using the...

No worries.

Mine is more convoluted, I know, but for a large table could potentially perform much better.

As long as you got a solution you could use 🙂

Gillian_Pappas2002 (1/16/2014)

If all of the customer's records have an QS class, those do not have to be updated at all. Only the same customer order records that have at...

No to both. Best is to use a set-based method, possibly like this one:

UPDATE tn

SET order_class...