Hi all,
I am very new to mssql server and would appreciate so input on my problem.
SCENARIO: I have a database that contains numbers that need to be recorded during a particular time span. A start and end. In a nutshell, these are personnel accountability numbers. Meaning, how many folks were in a particular department at such and such time. These numbers are manually inserted via html form by section heads...at any given time.
FIX ACTION:
What I thought about doing was taking advantage of a DTS/trigger package to run in 1 minute intervals. Ultimately, I'd like to do this 24/7 so "the boss" will not actually have to initiate a start time because it's pretty close to real-time, being at 1 min a piece. However, I am afraid this may be too much strain because let's face it, a lot of recs will be inserted in a 24 hour period. Any "food for thought" ideas on this? I am sure this is doable; however, is it bad design?
PROCESS:
A user inputs a set of numbers into database on the frontend
At the backend...SQL copies recs from accountability table then inserts into a archive table...allowing to produce a timeline. This timeline will obviously go up and down and should show accountability lows and peaks
My apologies for the length here. Am I going in the right direction here? Or is there something more adequate?
BTW, I have it working on the client side using javascript; however, if you drop the screen....the insert sql statement is to no use.
Your time and input is greatly appreciated
Brian
I am very new to mssql server and would appreciate so input on my problem.
SCENARIO: I have a database that contains numbers that need to be recorded during a particular time span. A start and end. In a nutshell, these are personnel accountability numbers. Meaning, how many folks were in a particular department at such and such time. These numbers are manually inserted via html form by section heads...at any given time.
FIX ACTION:
What I thought about doing was taking advantage of a DTS/trigger package to run in 1 minute intervals. Ultimately, I'd like to do this 24/7 so "the boss" will not actually have to initiate a start time because it's pretty close to real-time, being at 1 min a piece. However, I am afraid this may be too much strain because let's face it, a lot of recs will be inserted in a 24 hour period. Any "food for thought" ideas on this? I am sure this is doable; however, is it bad design?
PROCESS:
A user inputs a set of numbers into database on the frontend
At the backend...SQL copies recs from accountability table then inserts into a archive table...allowing to produce a timeline. This timeline will obviously go up and down and should show accountability lows and peaks
My apologies for the length here. Am I going in the right direction here? Or is there something more adequate?
BTW, I have it working on the client side using javascript; however, if you drop the screen....the insert sql statement is to no use.
Your time and input is greatly appreciated
Brian