Here is the Scenario :<BR><BR>I am using a table to temporarily store the records fetched from multiple tables. A store procedure fills in a data to this table and another Store-proc reads the data immediately and seletes the data once read.<BR>Now, to handle multiple simultaneous logins, (this table being accessed by many users at a time, so data may overlap), can I use Session Id as a unique identifier ? Or is there any other best solution ?