Viewing 15 posts - 53,926 through 53,940 (of 59,072 total)
Matt Miller (11/26/2007)
"Yeah - I was playing with this new cool TRUNCATE feature in production, right before the end of my last...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 3:53 pm
Heh... yeah, I know... "Bus-man's holiday" 😛 The really wide code is pretty tough on the display...
Yeah... I'm a "geek"... love this stuff. Some folks do counted cross-stich...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 3:45 pm
Pieter Huiberts (11/26/2007)
Would A CLR + .NET allow some type of batching, or setting...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 3:39 pm
You bet... as soon as you can get everyone that could ever have access to this forum to sign a "non-disclosure notice" and a "Covenant not to compete". That...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 3:29 pm
Heh... real problem is that Adam and a whole bunch of other folks think that what they've posted as a solution (including the one I "documentd"), are "Set Based". ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 10:44 am
Ananth,
How many rows are you talking about? It will make a difference...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 10:36 am
OP simply wants a running count, Karthick.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 10:21 am
Heh... BCP the data out to a file... use Bulk Insert to load it... amazing how fast it can be...
Should never have any "data errors"... data should already be gleaned...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 9:59 am
Heh... then there's that 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 9:40 am
Thanks, Rudy! That's exactly what I was looking for.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 9:38 am
The values are NOT the same! Look at what you have for "m"... not the same... none of them are the same...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 9:30 am
Sure thing and thanks for the feedback, Randy... if you have any other questions, please don't hesitate to ask.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 9:18 am
...but it could also result in code that nobody else knows how to maintain.
Heh... you should NEVER have that problem... "good" programmers also document their code especially when it comes...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 9:16 am
3 rd normal form
(or)
What's the database for?
What's going to be stored in it, for how long and why?
Who's going to be using this and how?
(or)
both
Both... you cannot design a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:57 am
Ahbijit,
Karthick doesn't need a "trigger"... what he said was...
I want to know about Database design. If we think about 'DataBase Design', which would trigger first in our mind ?
... and...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 26, 2007 at 8:52 am
Viewing 15 posts - 53,926 through 53,940 (of 59,072 total)