Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8144461
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T13:22:59+00:00 2026-06-06T13:22:59+00:00

So we are migrating from Informix to Sql Server. And I have noticed that

  • 0

So we are migrating from Informix to Sql Server. And I have noticed that in Informix the queries are written in this manner:

select [col1],[col2],[col3],[col4],[col5]
from tableA, tableB
where tableA.[col1] = table.[gustavs_custom_chrome_id]

Whereas all the queries I write in SQL Server are written as:

select [col1],[col2],[col3],[col4],[col5]
from tableA 
inner join tableB on tableA.[col1] = table.[gustavs_custom_chrome_id]

Now, my first thought was: that first query is bad. It probably creates this huge record set then whittles to the actual record set using the Where clause. Therefore, it’s bad for performance. And it’s non-ansi. So it’s double bad.

However, after some googling, it seems that they both are, in theory, pretty much the same. And they both are ANSI compliant.

So my questions are:

  1. Do both queries perform the same? IE. runs just as fast and always gives the same answer.
  2. Are both really ANSI-compliant?
  3. Are there any outstanding reasons why I should push for one style over another? Or should I just leave good enough alone?

    Note: These are just examples of the queries. I’ve seen some queries (of the first kind) join up to 5 tables at a time.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T13:23:02+00:00Added an answer on June 6, 2026 at 1:23 pm

    Well, “better” is subjective. There is some style here. But I’ll address your questions directly.

    1. Both perform the same
    2. Both are ANSI-compliant.
    3. The problem with the first example is that

      • it is very easy to inadvertently derive the cross product (since it is easier to leave out join criteria)

      • it also becomes difficult to debug the join criteria as you add more and more tables to the join

      • since the old-style outer join (*=) syntax has been deprecated (it has long been documented to return incorrect results), when you need to introduce outer joins, you need to mix new style and old style joins … why promote inconsistency?

      • while it’s not exactly the authority on best practices, Microsoft recommends explicit INNER/OUTER JOIN syntax

      • with the latter method:

        • you are using consistent join syntax regardless of inner / outer
        • it is tougher (not impossible) to accidentally derive the cross product
        • isolating the join criteria from the filter criteria can make debugging easier

    I wrote the post Kevin pointed to.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am migrating from PHP4 to PHP5 I have this in my .htaccess: php_flag
Currently migrating from SQL Server to PostgreSQL and attempting to improve a couple of
I'm migrating from SQL Server to Firebird. In SQL Server CREATE PROCEDURE Departments_GetAll AS
I'm migrating from SQL Server to PostgreSQL. I've seen from How to declare a
We are migrating from an ASP.NET/SQL server setup to a rails/mysql setup. Because of
I have been migrating from subversion to mercurial piecemeal and this has created a
I'm migrating from Java 1.1. to Java 5. I notice that some methods have
I'm considering migrating from Heroku to Rackspace Cloud Server, but I have few questions.
We have a system that is migrating from an older VARCHAR using LIKE setup
After migrating from Grails 1.3.7 to 2.0.4 I have noticed a problem with one

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.