Viewing 15 posts - 54,361 through 54,375 (of 59,098 total)
James Stover (11/4/2007)
"What's that you say Mr. Web Developer? Just "put it in"? Sure, I'll stay up to 3am troubleshooting & optimizing your masterpiece while you are...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2007 at 6:40 am
what is good to "beef up" a resume
Ummmm... How about a couple thousand posts on a high quality forum like SQLSeverCentral.com ???
Or, how about a list of major...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2007 at 8:53 pm
Wow... thanks for the kudo, Steve. Thanks.
I read that blog article... Michael J. Hillenbrand is pretty much spot on except maybe for the order of the first two things......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2007 at 5:58 pm
Sorry, I didn't check my post and I submitted it... I had included backslash n and apparently, it didn't take on this forum....
Have you tried backslash n ??
(and, now you...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2007 at 5:01 pm
Jason Coleman (11/3/2007)
LOL - toooooo many late nights reading forums... 😉Still, I read in BOL that you have little control over the page format when rendering to Excel. Bummer.
You...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2007 at 7:55 am
*= is severely deprecated and may produce unexpected results. Don't use it.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2007 at 10:03 pm
Have you tried using SELECT/INTO using QUOTENAME for each column?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 11:28 pm
Heh... now THAT's entertainment 😀 Would have loved to see their faces...:w00t:
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 10:18 pm
So post what you've tried so we can coach you...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 10:11 pm
Ugh! A "Sequence" table... I hate 'em... If you don't already hate 'em, you will.;)
Ok, David... let's pretend that the following is what your 3rd party sequence table looks...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 9:59 pm
You don't appear to have anything to relate the given values to logical rows... have you posted all the columns that appear in these tables?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:45 pm
The system has to be able to see the file to load it... make sure SQL Server Services use a startup account that can see the path to the file.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:39 pm
Heh... did you convert the correct column? Only way you can get that error is if the target column is actually an INT... double check the schema and make...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:24 pm
I think you would be unhappy... unless there's a pot wad of extra money involved... in which case, you'll still be unhappy but more satisfied 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:22 pm
What are you using to determine the size of the table?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 2, 2007 at 8:19 pm
Viewing 15 posts - 54,361 through 54,375 (of 59,098 total)