Viewing 15 posts - 52,636 through 52,650 (of 59,091 total)
Dunno what to say... like I said, the following code which you posted, works fine on my machine... no errors of any sort...
[font="Courier New"];WITH T1 AS
( SELECT CAST('2007-01-01' AS DATETIME)...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 11, 2008 at 6:30 am
Of course, not being always swayed by "official" documentation, I've tried it... only to be frustrated by the very same error messages as Kalhara was. I'd have to agree...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 7:44 pm
Ok... understood...
Run the following query from SSMS and let's make sure that the "server" (your Developer's Edition) can see the file...
EXEC master..xp_fileexist 'C:\Program Files\Microsoft SQL Server\MSSQL\Binn\add.dll'
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 3:45 pm
I know... you said that before...
WHICH MACHINE is that on! Is it on the SQL Server or on your DESKTOP computer?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 12:57 pm
Now we're talking! Verifiable documentation from MS (usually) works for me! Thanks, Chris!
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 12:56 pm
Heh... maybe the 3rd time will be the charm...
PLEASE copy and paste the exact error you're getting... I get no errors when I run the code you posted in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 11:01 am
I'm going to say this so that everyone gets the point... 😉
No, No, No, No!!!!
Now that I have your attention, the reason why I'm being so adamant is because...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 10:23 am
All good replies... but they all seem to miss the mark a bit. This question seems to be more about what you can and cannot do with variables in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 10, 2008 at 9:55 am
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
Viewing 15 posts - 52,636 through 52,650 (of 59,091 total)