Starwatcher (10/30/2014)

---

kenambrose (10/30/2014)

---

very simple solution to all the nonsense.

MAKE ALL COLUMNS NOT NULLABLE.

If you can't figure out how to design a schema where that works for your business requirements,...

ZZartin (10/30/2014)

---

Robert Mark (10/30/2014)

---

I don't know how anyone using an application and seeing a NULL value on the screen would equate the NULL value to anything other than a zero....

It sounds like you need something along these lines:

ALTER TRIGGER [dbo].[trU]

ON [dbo].[tblEvent]

AFTER INSERT

AS

SET NOCOUNT ON;

UPDATE c

SET avbl= CASE

WHEN i.[Desc]...

D'OH, quite right, sorry. "13" days should be added, not 19. ...

Yes, "Valued Member", that is basically correct, you do not use parameters like that in a trigger in SQL Server.

Do you really need/want two separate scripts? You can do this in one (complex) date computation:

SELECT

*,

DATEADD(DAY, DATEDIFF(DAY, 5, DATEADD(DAY, 19, DATEADD(MONTH,...

The trigger is firing. You must keep in mind that SQL Server only fires a trigger once per statement, no matter how many rows are INSERTed (UPDATEd or DELETEd).

Therefore,...

To check for anything other than only digits (0 thru 9), use:

NOT LIKE '%[^0-9]%'

for example:

SELECT

TextID,

CASE WHEN TextID NOT LIKE '%[^0-9]%' THEN 'OK'...

Everyone be aware that this is a school assignment; reposted perhaps to avoid disclosing that fact and get a "complete solution" instead of just helpful tips.

dariuslearn (10/23/2014)

---

ScottPletcher (10/23/2014)

---

Sorry [that did seem rather obscure for a starting class on SQL].

In the SELECT list, after the original column name or expression, you can add "AS new_column_name", and...

Sorry [that did seem rather obscure for a starting class on SQL].

In the SELECT list, after the original column name or expression, you can add "AS new_column_name", and the query...

I guess rename one of them. But better to avoid using temp tables in a trigger unless absolutely necessary.

The triggers probably need re-written. Post them here and we...

You can use system procedure:

sp_rename

to rename a column. The general format is like this:

EXEC sp_rename 'table_name.existing_column_name', 'new_column_name', 'COLUMN'

patrickmcginnis59 10839 (10/23/2014)

---

ScottPletcher (10/23/2014)

---

arnipetursson (10/23/2014)

---

ScottPletcher (10/22/2014)

---

You should be able to use the session_id to do the lookup. But since session_ids are reused, and sysjobactivity keeps history, if your proc...

I suggest gen'ing the MOVE clauses directly from @tables, ignoring the count. Just concatenate all the results into a RESTORE statement, and run that statement dynamically. For example:

...existing...