We use Sql Server as a backend to the Medical Sw that we use. We have two depts that use this Peds and Adults. When we the Peds Dept do our charts we still see all the Adult stuff as well. Is there a way to set it up on SQl that will allow us to separate our stuff from the adults? Sometimes we need to make changes that really do not apply to them and visa versa. I was thinking that in SQL we could just use separate tables one for Peds and one for the Adults. Or would it be necessary for us to get a separate server in order to house our side. Or is this something that we should be able to do from the Medical SW Side? We would like to be able to support our own side of things without having to go thru the Adult side to get things added, deleted or changed!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Questions Re: SQL Server 7.0
- Thread starter Shiloh917
- Start date
nigelrivett
IS-IT--Management
Depends if this is one system or two.
It sounds like it is one system that has some different functionality depending on the type of record. You would normally implement this in the application or the stored procedure layer depending on the nature of the difference.
Without knowing more about the system it's difficult to give an answer - maybe peds and adults need different attributes but whether they should be differemnt tables or have a joint master table and different attribute tables or just unused attributes on the single table it's not possible to say without some data analysis.
You won't need different servers - although this may be beneficial from a businesss aspect. Different databases on the same server is a possible requirement though if the systems are very different.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
It sounds like it is one system that has some different functionality depending on the type of record. You would normally implement this in the application or the stored procedure layer depending on the nature of the difference.
Without knowing more about the system it's difficult to give an answer - maybe peds and adults need different attributes but whether they should be differemnt tables or have a joint master table and different attribute tables or just unused attributes on the single table it's not possible to say without some data analysis.
You won't need different servers - although this may be beneficial from a businesss aspect. Different databases on the same server is a possible requirement though if the systems are very different.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
- Thread starter
- #3
It is a one system with different functionalities. We just would like to see only the Peds side of the functions so I am thinking maybe a joint master table with different attribute tables may be what I am looking to do. This would allow us on the Peds side to just see the templates that apply to us would it not?
Thanks!
Thanks!
- Status
Similar threads
- Locked
- Question
