Viewing 15 posts - 56,131 through 56,145 (of 59,071 total)
Found another good reason not to use "parameterized scripts" as embedded SQL... see the following recent URL about the wrong execution plan being created...
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=373799
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2007 at 6:38 am
"Precisely" ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 14, 2007 at 6:36 am
Going back to the basics, why not just create a linked server to the Access database and use SELECT/INTO? Will create the table and copy the data rather "automagically"...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 8:39 pm
Heh... no... they only paid me the big bucks to round UP your minutes ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 8:26 pm
Why can't you change it? Because it's 3rd party???? or ????
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 12:07 pm
You're saying the format of a given text file changes a lot??? Do the text files have header information on the first line of the file?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 12:03 pm
Nope... can't be done in EM... open the view code in Query Analyzer first... save the old code... copy the code to EM... experiment with changes... copy/type the changes into Query...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 11:59 am
That's cool... do you know if table variables still have the same fault of not being able to use statisics and not be alterable once formed?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 11:51 am
I agree with you both... one of the more import facts is that a lot of folks who write SQL code embedded in whatever app they're writing, have no real...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 11:48 am
Now we're cookin'... nicely done.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 11:26 am
No... no query... the recommendation was to use a "Calendar Table"... there are many to choose from if you search this site.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 11:21 am
Just curious... why do you need a single column?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 11:19 am
Just a bit of a follow up on the suggestion that dates and times be formatted by the GUI...
If you have an international presence, many GUI's can be "programmed" to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 10:18 am
Was actually wondering when you'd show up on this, Mr. Burrows... you normally have some pretty good tricks up your sleeve
I'm going...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 10:11 am
Very cool... Thanks for taking the time to explain in such great detail. Just for grins, I also checked Excel... the standard rounding functions don't appear to do Banker's Rounding...
Actually,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2007 at 10:06 am
Viewing 15 posts - 56,131 through 56,145 (of 59,071 total)