Let us try to examine for ourselves with an example.
To get started, use the following script, which I ran on my sever to create a table OrderTest in database TempDB and, additionally, to insert 4 rows into the table.
We are ready for the test. Let us select data from the table.
The results are indeed retrieved in the order in which it is inserted. Convinced?
Now I am going to add a primary key to the table.
With the primary key in place, let us once again select data from the table using the previous select statement.
The rows are NOT returned in the order in which it is inserted!! Surprising??
What made the difference?
In the first case, the SQL Server query optimizer decided to do a table scan while it opted for a Clustered Index Scan in the latter case. See the following execution plans for an illustration.
The verdict.
SQL server does not guarantee any order of output (unless you explicitly append an ORDER BY clause to the query to order your output in a desired way added). Further, it is the SQL Server query optimizer that decides how the data should be retrieved. Hence never assume that data will be returned in the order in which it is inserted.