Viewing 15 posts - 286 through 300 (of 1,217 total)
Log table is just MY name for a table into which you insert rows from a trigger. It is not a system table. You did not post the trigger, so...
September 20, 2007 at 8:23 am
Insert trigger is fired every time when you insert into the table.
If you want to know when it was fired, make column date_created in your log table. Then make the...
September 20, 2007 at 6:14 am
Sorry, subu, I don't get it... are you creating triggers inside of stored procedure? Or are they already present in your table and the procedure should fire them? What "fired...
September 20, 2007 at 5:09 am
If you want to insert into the log all rows that were updated (regardless of whether something was changed or not), then your trigger should work. If you only want...
September 20, 2007 at 5:03 am
" but i get an error" ... what a wonderful definition of problem. Makes it really easy to find solution.
Here are some more ways how to ask for support (from...
September 20, 2007 at 1:24 am
Great idea, let me know when and where I can order that book .
September 19, 2007 at 2:43 am
Sure Lynn, I wasn't trying to tell that your method is wrong or anything like that... just that I personally prefer to avoid SET DATEFIRST. It is always good to...
September 19, 2007 at 1:22 am
Well, I admit that I didn't have patience to analyze Lynn's code, but it does not look simpler than the code I posted, and it uses SET DATEFIRST... so I...
September 18, 2007 at 9:08 am
Look for the post (reply) by Jeff Moden here
September 18, 2007 at 6:00 am
You probably misunderstood what Sergiy meant... you should create permanent Numbers (or Dates) table, once and for ever. Then you can use it in such queries as you described.
September 18, 2007 at 5:54 am
Well, it probably depends on environment. If you write a script that will apply changes in a procedure to several databases (like when several clients use "copies" of the same...
September 18, 2007 at 5:21 am
I'm a bit confused... Are you writing some stored procedure that modifies another stored procedure and then runs it?
Or are you asking whether you should drop and recreate a procedure...
September 18, 2007 at 4:04 am
Try this for starters:
SELECT a.deptname, c.deptname, COUNT(*)
FROM TableA a
JOIN TableC c ON c.userid=a.userid
ORDER BY 1, 3 DESC
It does not solve the fact that once a department is linked, it can't...
September 18, 2007 at 3:49 am
I'll try to repeat what I have understood... correct me where I'm wrong.
You have a table "old" that lists all employees, and to which department they belong.
You have a table...
September 18, 2007 at 2:17 am
You can do it using DATEADD and DATEDIFF functions, but how exactly, that depends on what should happen when you run the query on Wednesday (or with a day that...
September 18, 2007 at 1:26 am
Viewing 15 posts - 286 through 300 (of 1,217 total)