Viewing 15 posts - 51,796 through 51,810 (of 59,091 total)
The reason you're getting the file does not exist error is probably because of permissions. What ever user you SQL Services start up as, must be able to "see"...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 11:24 pm
Why not? VARCHAR MAX holds 2 billion + characters...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 10:44 pm
Indexed multi-table view... multi-table SELECT... which one will you call UPDATEable? Neither in all likely hood. An update would have to be something separate... paging isn't used to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 10:37 pm
That would be correct (about the XP's in 2k). Didn't mention those because didn't think they would apply here.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 10:34 pm
Matt beat me to it (more often than not, lately 😉 ) OUTPUT command in 2k5 will do it just fine.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 10:33 pm
If it's for a report, why not just leave it as NText all the way through?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 10:25 pm
If you don't mind the "pivot"...
SELECT
SUM(CASE WHEN DATEDIFF(dd, AsOfDate, GETDATE()) BETWEEN 1 AND 30 THEN 1 ELSE 0 END) AS [1-30],
SUM(CASE...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 10:17 pm
I really want to know why you're formatting numbers in SQL... that should be done in the GUI if there is one... and it looks like there is one. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 10:05 pm
Make the UDF accept the table name as an additional parameter and pass it. Just remember that UDF's can't do Inserts, Updates, or Deletes on tables nor can it...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 10:01 pm
First things first... please see the link in my signature line for the way to post table descriptions and data in the form of executable code... makes life real easy...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 9:54 pm
Heh... two words...
TALLY TABLE!
I'll be back in a minute with an example...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 9:33 pm
So tell me... why do you think any of that requires a cursor? Or am I misunderstanding your post?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 9:31 pm
Sounds a bit like homework or an interview question, but I'll bite...
In the presence of the correct indexes (composit primary key), the first one will probably be a little faster...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 9:06 pm
The real answer is that you shouldn't store the dashes... that's formatting and it really has no place in the database. I'd make the app strip out the dashes...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 9:03 pm
Poifect 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 8:58 pm
Viewing 15 posts - 51,796 through 51,810 (of 59,091 total)