CELKO (1/4/2013)

---

The power employees I work with regard me as the "Data...

CELKO (1/4/2013)

---

As I said, read books on basic Software Engineering. Yourdon and Constantine's STRUCTURED DESIGN is still classic. Chapters 6 and 7...

CELKO (1/4/2013)

---

I see that you also confuse rows and...

CELKO (1/4/2013)

---

Since SQL is a database language, we prefer to do look ups and not calculations. They can be optimized while temporal math messes up optimization. A useful idiom is...

Do you have only a few clients with huge numbers of orders each?

Or for a large number of clients, some with large numbers of orders, some with small numbers of...

Those embedded REPLACEs are looking more tempting now, huh? 🙂

dwain.c (1/3/2013)

---

ScottPletcher (1/3/2013)

---

That "we" is undefined and thus meaningless. But people who have...

Lynn Pettis (1/3/2013)

---

You mean something like this?

DECLARE @TestStr VARCHAR(20) = 'QWERY56920TYEU';

SELECT @TestStr;

WITH eTally(n) AS (SELECT ROW_NUMBER() OVER (ORDER BY (SELECT NULL)) FROM sys.all_columns a CROSS JOIN sys.all_columns b)

SELECT

...

Embedded REPLACEs is your best option really, from a performance standpoint.

You could generate the REPLACE statements so you didn't have to write them by hand.

.

GilaMonster (1/3/2013)

---

kwoznica (1/2/2013)

---

You also wrote

I take that this is a suggestion to make the phone_contact table a wider table to...

That "we" is undefined and thus meaningless. But people who have to write...

If you're providing data for report or any type of BI application, remove NULLs entirely. NULLs cause serious and severe logic considerations that most people don't fully understand (including...

dan-572483 (1/2/2013)

---

If all the queries in combined by the UNION statement are quering the same table (or differenet tables but the coumn names are the same), then you shoudn't need...

SELECT

OccurrenceReport.OccurrenceDate,OccurrenceReport.TimeOfOccurrence,OccurrenceReport.Floor,OccurrenceReport.Description,

OccurrenceReport.Injured,OccurrenceReport.FDNY,OccurrenceReport.FalseActual,OccurrenceReport.FPManager,

OccurrenceReport.DateSigned,OccurrenceCauses.Cause,

Emp.LastName + ', ' + Emp.FirstName as "EmployeeName",

FireM.LastName + ',...