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 |
|
nic
Posting Yak Master
209 Posts |
 Posted - 2003-01-06 : 20:22:54
|
| Hi,I'm in the process of creating a web application where users will apply for a product. This online form (multi-step) will be open to the general public so we are concerned there will be lots of random applications (some joe blow randomly filling out incomplete applications). Due to this we want to store incomplete applications in some temp tables. After completing the application and determining this is a REAL application we will copy the record to the real tables. My question is what should I call these temp tables? I don't really like to use temp as the tablename and for other reasons I can't use application table.Has anyone run into this before and what did you call these temp tables? (They will be referenced a lot and it would be nice if they were named something meaningful but I can't think of anything.random question but maybe someone has a good suggestionNic |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-01-06 : 20:51:33
|
| Assuming it's a continuation of this:http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=21365I don't know if temp tables will be effective, because once the session ends the temp tables will be destroyed. If someone wants to come back they'd have to start over again, and complete the entire application. If you used regular, permanent tables with the pre-application info, you can just transfer it to the normal table once everything's completed.Also, in a web environment, the web server will be connecting to SQL Server using its own account, so all of the web users will essentially use the same connection and, therefore, the same temp table(s). You'd have to provide a way to differentiate multiple sessions based on row value, not connection or table name, so you'd be no better off than using a regular table instead.Using a regular table also allows you to set up a scheduled job to delete the incomplete applications on a regular basis, so that they get cleaned up automatically. You can add a datetime column and have the job delete anything that's older than 48 hours, for example. |
 |
|
|
nic
Posting Yak Master
209 Posts |
Posted - 2003-01-06 : 21:01:36
|
| Yes it is the same topic (I got side tracked with a different app). When I said temp tables I meant regular tables. I'm just struggling with what to name these tables that store incomplete application information. This is just a naming convention question. I have these pre-application group of tables but tblTempApplicationUser, tblTempApplicationMain just doesn't sound good. I was curious if anyone who had maybe designed something similiar had any good naming conventions. (I realize this isn't a sql question but I struggle with giving my tables descriptive names)Nic |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-01-06 : 21:06:20
|
It really doesn't matter what you name them, as long as YOU can differentiate them from the other tables.  Maybe PreAppMain and PreAppUser, for example, and the regular tables would be AppMain and AppUser. |
|
|
|
|
|
|
|
|
random question web application db design