Viewing 15 posts - 55,351 through 55,365 (of 59,072 total)
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
Books Online doesn't have the info you want/need?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 8:51 pm
Outer joins are not necessarily a bad thing... it's the criteria (or rather, lack of) that is usually responsible for the notorious reputation of outer joins. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 8:49 pm
Based on the fact that the default is for the Primary Key to get the clustered index and the fact that you're trying to create a different clustered index... I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 8:47 pm
I'm sure that I'm preaching to the choir, but I gotta say it... make sure you have an up to the minute full backup of the database (maybe even a hot...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 8:40 pm
And, breaking a set of millions of rows up into smaller sets still isn't RBAR... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 15, 2007 at 8:27 pm
I wouldn't be surprised if it was a Java or C# batch job running at that time
SQL Scheduled Jobs aren't the only show...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2007 at 10:51 pm
Thanks for the awesome compliment, Kenny... and thanks for the patch to the code!
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2007 at 6:58 pm
| I really don't care how bad the query was or care about optimizing it. All I wanted... |
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2007 at 6:30 pm
Yeah... Sorry about that... was thinking about something different and didn't double check. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2007 at 6:16 pm
Whatever... I've been working with SQL Server for 12 years and I've never had to write a cursor. Yeah, sometimes the occasional While loop in a function (have even gotten...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2007 at 6:09 pm
Thanks, Edward. Take a look at the above, if you want.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 14, 2007 at 5:58 pm
Viewing 15 posts - 55,351 through 55,365 (of 59,072 total)