Viewing 15 posts - 52,651 through 52,665 (of 59,098 total)
All good conversation and good information from all. Guess the answer to the OP's question should be, "Yes" or maybe even "Yes, most definitely". 😀 Some of...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 9:46 am
Dennis D. Allen (2/6/2008)
CREATE FUNCTION dbo.DateRange( @start DATETIME, @length INT )
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 9:04 am
jerryhung (2/6/2008)
that is not VERY VERY fast. Anyway, we don't have the need for it, I was just curious
16...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 8:30 am
susheereddy (2/8/2008)
its in my specified folder
The server needs to be able to "see" and "read" your "specified folder". That's why I was asking what its physical location was.
Good luck.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 8:01 am
AM,
Ian is absolutely correct... for very small groups of rows by account, the example he gave will work just fine albeit a little slower than you may expect (just as...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2008 at 10:23 am
Is that file path on the server... or on your desktop box?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 6:13 pm
"New" view, available in 2k5, is called sys.Objects and will likely be available in 2k8, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 6:12 pm
I don't think I wrote an article on "DateDiff Usage"... so it would be interesting to find out how my name got on this...
Anyway, nice trick you've found. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 6:06 pm
And, maybe learn how to post sample data to get better answers...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 5:53 pm
Heh... right there with ya, Gus... seems like the long way to spell "Death by SQL", though 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 5:39 pm
That should do it... nicely done, John.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 5:07 pm
You said that you wanted to pass parameters to the stored procedure in the trigger. That smacks of RBAR and single row processing which is a form of "Death...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 5:05 pm
Then, you need to post the exact code you're getting the error with and the exact error... because the code I posted gives no such error on my machine. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 4:08 pm
Radovan Jablonovsky (2/8/2008)
If it is possible in your production environment to dynamically change number of processors, then it is OK. In our environment it is more conservative, therefore I am...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 4:04 pm
I absolutely agree, Matt... same thing goes with the SUM() OVER... they (MS) don't allow the necessary ORDER BY to calculate a running total using SUM() OVER like they do...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2008 at 7:10 am
Viewing 15 posts - 52,651 through 52,665 (of 59,098 total)