![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
when there are more records for e.g. 100000 or more , it changes the logical order of data |
#3
| |||
| |||
|
|
when there are more records for e.g. 100000 or more , it changes the logical order of data Are you referring to the perceived order in the table? Rows in tables have NO logical order in a relational database. If you require a particular order you have to query them using a SELECT statement with an ORDER BY clause otherwise the ordering is undefined. If that doesn't answer your question then please describe your problem with DDL (including keys), sample data INSERT statements and show your required end result. -- David Portas SQL Server MVP -- |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
While inserting records in hash table. It is already order by on some fields. |
|
But when selecting/updating records, I want the same order of records should be updated/selected. "Rows in tables have NO logical order in a relational database" I think, True for hash(#) and permanent table. |
#6
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |