MS SQL Tables with no index

I need to convert a cloud based database to an internal MS SQL 2008 database and one issue I have run into is that none of these tables have any indexes declared. Now this causes me concern for several reasons but the one that stands out immediately is that in new code I have written around one of tables requires a set of rows to appear in a certain order. So a simple query was select itemnmbr,itemdesc from my table where categoryid='XX' order by seq. Where what I thought what this would give me is all items that are in category XX sorted by the seq number. However, I quickly discovered that they do not use the seq number field. They are all zeroes. So much to my amazement the correct order is always achieved by simply select itemnmbr,itemdesc from my table where categoryid='XX'  with no order by clause. How is this possible? How can they be adding records to this table through their code and somehow always maintain the proper sort order without the use of an index? Is there some internal SQL database table structure element they are controlling?
Who is Participating?
Dave BaldwinConnect With a Mentor Fixer of ProblemsCommented:
If they are inserted in order, they will usually be returned in that order until you start changing and deleting records.
Anthony PerkinsConnect With a Mentor Commented:
If they are inserted in order, they will usually be returned in that order
I am afraid that is simply not true.  Unless you use an ORDER BY clause the order returned is not guaranteed. Period.
rwheeler23Author Commented:
There is no identity column either. The old website is a collection of very small data tables. The biggest table is about 3000 records and items are grouped into category. All items within any group share common properties and it is these properties that concern me. These properties appear across the top of each page and provide detailed information as to how the item is configured. There are about 60 categories. I have be checking and so far every time I ask for the list they come out in the order desired. I just do not know how that is happening. The good news is on my side there will be a column that puts items in the proper order so the real proof of the pudding will be after I insert all the items into my table, I do a cross comparison with the old table to see if they all came over in the correct order.
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

dqmqConnect With a Mentor Commented:
>so far every time I ask for the list they come out in the order desired.

We'll they will come out in some order, right?  And since there is no clustered index, the db is quite likely to just store them in the order inserted and return them in the order stored  So, coincidentally, they could be coming out in the order desired.  But, I do mean coincidentally and you cannot depend on it.  Even if you're cross-comparison checks out, you cannot rely on the order unless you stipulate one in an order by clause.  Agree with ACPerkins on that.

And, for that matter, if the old table does not have columns that convey the desired order, then I'm quite puzzled how you might derive or validate the seq column in the new table. And even if you do get the desired order 100 time in a row, without an order by clause you've proved nothing.

I'm glad you have the foresight to add the seq column in your internal DB.  You're fortunate to have the data somewhere to reconstruct the desired order.
rwheeler23Author Commented:
I agree completely. I was surprised when I saw nothing but zeroes in the seq column. When I first looked at the structure of the table I said, that is the field I need. Then I looked at the data and was surprised. This is a one time transfer. So what I will do is have a copy of the order on the old website and then manually compare the sort order to the new web site. If I find any differences I will update my table.
DcpKingConnect With a Mentor Commented:
What database system are they using on this cloud system? (obviously not SQL Server or Oracle, it seems). If you can find that out then maybe we can discover what the developers did ...
Scott PletcherSenior DBACommented:
>> you cannot rely on the order unless you stipulate one in an order by clause. <<

That could depend on the specific db being used.  

While the ANSI standard states that for relational dbs, and other relational dbs follow that rule, there is no guarantee that whatever db engine is used to store the original data does not have its own rule that is different.  We don't know if the original db is even relational.
This is correct, Scott - even something like SQL Server will appear to behave like this in certain circumstances!

rwheeler23: Although knowing the environment for the original developers would be nice, you're constrained to working with your environment - SQL Server - to achieve your goals. I would suggest that you really do need to key and index your tables.

Which version will you be using, BTW? 2012 has a nice addition for the SELECT statement that help when you're supporting a paged display (on a web page, for example).
rwheeler23Author Commented:
Sorry for the trady reponse but I have been out of town and out of touch.

This is were the current MS SQL database resides. I was able to connect to it using an instance of my instance of SQL Sever 2008. I have imported the entire database and will proceed with trying to analyze the table relationships.
rwheeler23Author Commented:
All I know is that they did come out in the correct order with no order by clause. I dumped them all into my SQL table this time indexed with a sequence number. Thank you everyone for responding.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.