Re: 1 server 2 SQL apps

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Citizen (citizen_NOSPAM_at_hotmail.com)
Date: 06/30/04 

Date: Wed, 30 Jun 2004 10:17:12 +0200

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.

Relevant Pages

  • Idiomatic Expressions to Operating System Architecture: Transforming Rigids
    ... <Subject: Re: Idiomatic Expressions to Operating ... <endpoint during a single session * DATABASE + by ... <statements is a new feature of SQL Server 2005. ...
    (sci.math)
  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: MS Access DAO -> ADO.NET Migration
    ... full SQL Server and I see the logic you explained in a multi user ... allow two users to access the same database file Read/Write at any given ... The book was a pleasure to read after the gibberish that Microsoft 'puts ... Hitchhiker's Guide to Visual Studio and SQL Server ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MS Access DAO -> ADO.NET Migration
    ... For that it is much harder to handle the incremental identifier, ... database but although they have the data, they are not connected at the same ... The book was a pleasure to read after the gibberish that Microsoft 'puts ... SQL Server Management Studio is nowhere to be found on my ...
    (microsoft.public.dotnet.framework.adonet)