g.britton (11/21/2014)

---

good point, though the...

I use a different approach.

I have a nonbusiness dates control table where one first defines the general and specific nonbusiness dates wanted. Then you call a stored proc with...

You don't "have" to do the FETCH twice. In fact, I never do that, because it's too error prone when the code is changed.

First, start over...

Jeff Moden (11/20/2014)

---

ZZartin (11/20/2014)

---

There's a difference between a service account login used by an application to connect, which a dba should know as the dba is likely the one who...

No, DBAs should not know and definitely not store end user passwords, period.

App passwords are a different matter, and it can depend on the app. But stored passwords should...

You can't calculate "work hours" without "in" and "out" markers. The work time calc is very easy if you a matching "out" for every "in".

In other words, you need to create a new table that explicitly specifies the clause:

CREATE TABLE ... (

...

TEXTIMAGE_ON [new_filegroup_name]

...

It's almost certainly the NTEXT that is the bulk of the data, and you can't move it without recreating the table entirely. Btw, you should change the ntext to...

No, that's true, but you could use it in a view.

I wasn't not sure what '20140601' was relative to the run date. Is it the current month, the next month, 6 months ago?

Therefore, I used @month_1 to hold the...

swhetsell (11/20/2014)

---

ScottPletcher (11/19/2014)

---

Probably the big thing is to reduce all the gyrations around UnitLog. Please try the query below. If you tend to restrict UnitLog rows using fldDateTime...

NULL will never be "LIKE" or "=" anything. To allow NULL values, you'd have to add:

WHERE (column_name LIKE '%' OR column_name IS NULL)

Try "LIKE" '%' rather than "=" :-).

Something else to check:

Did you explicitly specify the schema name of the table on the ALTER?

If not, make sure you are not accidentally working with a similar table / table...