Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mittal_pradeep
Starting Member
5 Posts |
 Posted - 2005-10-21 : 17:59:00
|
| My process includes following processes for various clients.- loading excel file into a sql database- Processing loaded data in sql tables- Dumping excel reportsI implemented these three stages by using set of physical temporary sql tables (not the memory ones with # and ##) for data transformations etc. I used to delete the data in these temporary tables and reuse for the next client. Till now I was the only person taking care of complete thing.Now I want to add multi-user capability to the system. I feel the only way to implement this is to change all my physical temporary sql tables to memory temporary tables i.e. using (# ## tables). But sql statement in data transformation task does not takes # tables. So I will have to dynamically change the sql to have # tables.Is it ok to load 20k records into memory for each client at the same time. Or is it a good idea to use physical temporary tables i.e. seperate physical table for each client and delteting it at the end. Also implementing client level locking in separate table.Am I thinking in right direction. Please suggest. |
|
|
|
|
|
Multi user capability