Viewing 15 posts - 51,586 through 51,600 (of 59,098 total)
Sure... go to the same source you found the info for the undocumented sp_MSForEachTable and find sp_MSForEachDB.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 8:34 pm
Just a programming note... the method that Matt used is a lot faster than recursive CTE's like the one you have over the long haul...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 8:32 pm
Thanks for sharing... but your CTE has an error in it... it won't return all of the days of March... it misses the last day because you of the <...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 8:30 pm
This is an SQL Server forum... and SQL is not SQL between RDBMS's... if you want MySQL help, I suggest you find a MySQL forum or refer to the documentation...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 8:20 pm
A "UniqueIdentifier" datatype and a default of NEWID() would probably fit the bill (although, I don't care for them. Lookup both items in Books Online for more details.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 8:18 pm
That would have been a good one to ask for some data on... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 8:15 pm
For what? Got an example of the PL/SQL that you're talking about?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 8:04 pm
To solve the problem of both auditing the initial change AND make life a bit easier on the type of "fired" recovery that you're talking about, without the additional overhead...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 8:01 pm
tuseau (3/19/2008)
Basically...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 4:01 pm
Matt Miller (3/19/2008)
Gareth Williams (3/19/2008)
Thanks Jeff for your help. I thought that might be the answer but hoping not.
I have to ask - what happens to all of the previous...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 3:55 pm
1) I can use a cursor in the trigger to get all the records from the Inserted table and populate the temporary table.
(Assuming that Inserted table has only records...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 3:45 pm
Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 3:42 pm
Heh... guess that's why they call it "Mumps"... sounds like a real pain in the neck 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 3:40 pm
GSquared (3/20/2008)
On the use of Insert in the trigger, that gives me a date the data was first created, and by whom. I don't like having "CreatedDate" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 3:35 pm
Just a couple of suggestions... some in the form of questions...
First, what is the purpose of an audit log? Think about it carefully... what is the ONLY purpose for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2008 at 2:30 pm
Viewing 15 posts - 51,586 through 51,600 (of 59,098 total)