Viewing 15 posts - 44,896 through 44,910 (of 59,095 total)
Thanks, Lowell... that's an awesome compliment. They'd probably just make the same excuses as everyone else, though... things like "it's good enough for what we want to do" or...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 11:09 am
alexander.yuryshev (3/1/2009)
Jeff Moden (3/1/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 11:06 am
Heh... and IMHO, CLR's have virtually no place including UDF's. RegEx and file handling are the only two places I've not been able to beat a CLR with T-SQL.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 9:49 am
Ross McMicken (3/1/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 9:32 am
Stanley Pagenel (2/28/2009)
Thanks Jeff my problem is fixed now
Yeah, I saw how you think you fixed it on the other thread of yours... lemme tell you the same thing I...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 9:26 am
Stanley Pagenel (2/28/2009)
Thanks Dugi that help me fix my problem.Have a nice day,
Stan
Nope... if all you've done is replace a Cursor with a Temp table and While loop, all you've...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 9:25 am
GilaMonster (2/28/2009)
Jeff Moden (2/27/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2009 at 8:33 am
Here's one, straight from the horse's mouth....
http://technet.microsoft.com/en-us/library/ms131075.aspx
The part that they left out is that there's normally a way to do the same thing in more than 95% of the case...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 9:46 pm
Google "UPSERT SQL SERVER 2005".
Basically, you need both an UPDATE and an INSERT. Both would have joins between the two tables. For the UPDATE, if the join succeeds,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 9:36 pm
If you were to go through the code and document it, I'll just be you could figure it out yourself. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 9:23 pm
Make the view without the WHERE clause. Use the WHERE clause when selecting from the view.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 9:05 pm
Stanley Pagenel (2/27/2009)
The procedure is use to set a flag in the table RRF_FICH_GPS_BRUT
Based on what? What are the business rules?
Also, please see how to post sample data in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 9:01 pm
SELECT @CompanyID = company_id FROM updated
Your code contains the line above... there's no such thing as an UPDATED table inside the trigger. Do you have a table outside the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 8:59 pm
MrBaseball34 (2/27/2009)
So you must ALSO create a TSQL wrapper for them. Man, what good is having to do that?Someone must be nuts to use CLR SPs...
Heh... finally... someone besides me...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 8:47 pm
Christopher...
Let's think about this... what harm would it cause if all the items were equal and we still did the update anyway? Unless you have triggers or a TIMESTAMP...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 8:36 pm
Viewing 15 posts - 44,896 through 44,910 (of 59,095 total)