Viewing 15 posts - 46,171 through 46,185 (of 59,101 total)
If there's nothing in the file that violates either privacy or policy, my recommendation would be to attach the file to a post and let us take a crack at...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:10 pm
aziz.kapadia (12/31/2008)
Can I declare table variable as output parameter in stored procedure?
Probably of more importance, what is it that you're trying to do? You'll be amazed at the possible...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:06 pm
Grant Fritchey (12/31/2008)
Thanks for the correction. I wasn't sure and I haven't really looked at the table valued parameters yet. I should have kept my mouth shut.
Heh... nope... then I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:04 pm
So! You carry the cell phone to the barn... when ya goin' for the implant, pal? ;):D:hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 4:08 pm
Good golly... I'm glad I'm not the only one that believes in the usage of well formed and safe dynamic SQL. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:56 pm
NULL (1/2/2009)
DECLARE @Tour TABLE (tourID INT IDENTITY PRIMARY KEY
,tourName VARCHAR(50)...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:35 pm
DBAdmin (1/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:29 pm
RBarryYoung (1/1/2009)
Heh. Gail is much faster than me... 🙂
Heh... while that may be true, your patience and depth of explanation are noteworthy. I'd have killed and eaten...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:25 pm
I've really got to respectfully disagree... the use of a "sequence" table of any kind will become a major hotspot, a possible source of a huge number of deadlocks, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:19 pm
Oh... almost forgot... the code I posted allows you to reserve more than one ID using an "increment". If you can't figure out how to use that for more...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:08 pm
mweber26 (1/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:07 pm
Grant Fritchey (1/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 2:56 pm
Steve Jones - Editor (1/2/2009)
I think it's as likely that it's thrown in there to limit the candidates as it is just an addition by HR...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 2:50 pm
bnordberg (1/1/2009)
Further I think single industry experience is a detrement. For example in healthcare (At least...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 2:38 pm
RBarryYoung (1/2/2009)
But when replacing cursors, we are letting go some important features that only cursors can provide to your code.
Assuming that we are talking about SQL Server 2005/2008, I know...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 2:31 pm
Viewing 15 posts - 46,171 through 46,185 (of 59,101 total)