Re: 1 server 2 SQL apps
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 06/30/04
- Next message: dj: "using nvarchar"
- Previous message: Tibor Karaszi: "Re: Upgrade from evaluation version in XP"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 30 Jun 2004 12:45:33 +0200
Why would service for one department affect uptime for the other department? Are you saying that you
have such service so you have to stop the SQL Server service? Ouch!
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Citizen" <citizen_NOSPAM@hotmail.com> wrote in message news:fdt4e0126bbhlok9f8t19eoprk032ug6d0@4ax.com... > On Tue, 29 Jun 2004 09:49:35 -0500, "Keith Kratochvil" > <sqlguy.back2u@comcast.net> wrote: > > >(1) [two different departments] > >I don't really understand this "need." What benefit would it be to stop one > >instance and not the other? Also, if you are purchasing the standard > >edition of SQL Server it is my understanding that you will have to purchase > >a copy for each instance that you want to deploy. Two instances = two > >copies of SQL Server. > > Well, one department has bought one SQL server application and has > data that is private to this department only. The other departement is > running another bought application and this data should be kept > private also. When one application needs updates or other maintenance > services the other department have to stop working also. So they would > have downtime for no reason. In the ideal situation we would have had > 2 separate servers. > > >(2) [security] > >It is possible to set up security at the server level (SQL Logins, NT > >Logins, Application roles) and assign the approrpiate ones to each database > >as appropriate. Of course you will have separate stored procedures within > >each database. In your example you will probably want to have two user > >databases. One for department A and one for department B. I am assuming > >that these departments have databases with different names. As far as the > >software developers not messing up the other data....there is only so much > >id10t proofing that can be done. > > OK thanks. I will keep this in mind and check whether the > downtime-issue is still a priority for everyone.
- Next message: dj: "using nvarchar"
- Previous message: Tibor Karaszi: "Re: Upgrade from evaluation version in XP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|