Viewing 15 posts - 37,801 through 37,815 (of 59,098 total)
Joe Celko (7/3/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2010 at 10:26 am
My advice would be.... don't do it.
UPDATE:
The advice above is incorrect. Please see my post below at
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 6:44 pm
rajendra prasad-377679 (7/2/2010)
hi dudehey can u send me the sample table with queries by using trigger..
Regards
prasad
So! Dude! What did you end up doing?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 6:10 pm
Aren't those just ODBC functions?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 6:06 pm
TKyle (5/26/2010)
Quick question. Is is possible to calculate the running total in Jeff's script without updating a table, i.e. in a select statement? This is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 6:04 pm
haggisns (2/8/2010)
An elegant solution would be great to have and I could learn from it! 🙂Thanks
Chris
So! Did you learn anything from it? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 5:50 pm
noor3rb (5/15/2010)
1- First Table called "Accounts" which have the following fields
AccountIDAccountNameParentIDLevel
1x null0
2x111
3x1122
4x11133
5x11233
6x1222
7x12163
8x12263
9x12363
10x211
11x21102
12x211113
13x2111124
14x2112124
15x2113124
16x22102
17x221163
18x222163
19x223163
20x311
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 5:40 pm
deeomen (6/4/2010)
--------------------------------------------------------------------------------
hi all
very new to sql
i have one table, with 7...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 4:42 pm
Ah... I believe I see... the forum code (or something else) added a spurious CR character. If you get rid of it, the previous code works just fine.
DECLARE @test-2...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 4:35 pm
skcadavre (6/30/2010)
DECLARE @test-2 AS TABLE(
id INT...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 4:30 pm
Jeff Moden (6/10/2010)
scott.pletcher (6/10/2010)
You might want to look into the use of [0-9] and [^0-9] just to simplify the code a bit.
Except I've had some odd results sometimes from that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 4:28 pm
Navi's (6/30/2010)
I am getting the same error..
"Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32)."
Can you tell me is it comes due to trigger call.
In my case,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 4:11 pm
Sean Josiah-454849 (7/3/2010)
thus systems have to have 100% uptime, people can't get sick or go on vacation, and nothing fills the round file. yet the world keeps spinning, and todays...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 1:46 pm
xzd000 (7/3/2010)
The emphasis is that - The table does not have primary key column. Does that fact...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 12:03 pm
Heh... I do find it amazing that certain types of data are considered to be NOT mission critical... that is, until it's lost. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2010 at 11:57 am
Viewing 15 posts - 37,801 through 37,815 (of 59,098 total)