Viewing 15 posts - 55,366 through 55,380 (of 59,098 total)
Where are the tabs located in the text file?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2007 at 9:33 pm
!= is what most GUI folks write and it's a bit more difficult to read than <>. Other than that, no difference.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2007 at 9:31 pm
What is the datatype for startdate and starttime? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2007 at 9:26 pm
Nope... don't need the conversion to varchar for date or time.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2007 at 9:24 pm
Since he's converting to DateTime, I'd suggest doing neither. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2007 at 9:23 pm
| Incidentally, if you're using SQL 2005, you can jump straight to the final result fairly elegantly |
Glad to see...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 10:49 pm
Heh... for the same reason most British don't measure heat in British Thermal Units? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 10:43 pm
There is nothing in the code that needs dynamic SQL. Rewrite the code to take variables. Normally, the only time you need dynamic SQL is for variable table or column...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 10:09 pm
Not sure what they call it in 2k5, but have you done a search on Bulk Copy or BCP in Books Online?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 10:04 pm
David is correct...
First, move the SET NOCOUNT ON statement to before the IF. There's a lot more at stake than just performance if a GUI is involved (pevents false...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 10:01 pm
They left off one very important disaster... and that's what happens when you have normal, healthy database growth and the code written against the database reaches a "tipping point". Lots...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 9:56 pm
I've never found a performance difference between the Ansi INNER JOIN and the Equi-joins found in a WHERE clause. And, contrary to what Remi has experienced (not an argument, just...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 9:17 pm
Just and FYI... there are many times that SQL code simply can't be tuned for performance and will need to be rewritten... sometimes, from the ground up.... 1 to 4...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 9:04 pm
Also, check out GROUP BY and Aggregate Functions in Books Online. You may also want to try the free tutorial at W3Schools.com... won't teach you the specifics of SQL Server but...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 8:58 pm
Correct... I don't believe 4.0 supported correlated sub-queries as appears in the suggested code.
Recommendation would be to see the documentation for 4.0 at MySql.com...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 8:54 pm
Viewing 15 posts - 55,366 through 55,380 (of 59,098 total)