[dba-SQLServer] Upsizing and consolidating Access data

Steve,

Actually, if you setup the site to use the ASP.Net 2.0 login scripts,
you can have as many logins as you want at the application level and not
worry about at the SQL Server level. You would just link the User info
from the tables created by the setup program to your HazMat tables.
I have done it for simle name and address dbs and it works quite well.

Robert


At 10:25 AM 5/17/2007, you wrote:
>Date: Thu, 17 May 2007 09:30:49 -0500
>From: "Steve Erbach" <erbachs at gmail.com>
>Subject: Re: [dba-SQLServer] Upsizing and consolidating Access data
>         into SQL        Server
>To: dba-sqlserver at databaseadvisors.com
>Message-ID:
>         <39cb22f30705170730s35acae7bqd3061f2fa446e7ee at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Jim,
>
>? That sure is a pretty application. ?
>
>Why, thank you, Jim! I'll pass that along to my wife, Janet; she was
>the graphic designer.
>
>I don't think that going down will be a concern.  This application is
>mostly used once a month to record data for the previous month to
>report out to the various guvmint agencies.  It's time critical to a
>degree, but everybody knows to get the info into the system on a
>timely basis for monthly reporting.
>
>I'm thinking that it's pretty workable, too.  The only question mark
>with respect to the web host is what will the extra charge be for
>additional SQL Server logins.  I think that would be the way to go
>instead of using one master login to save a few bucks and then having
>separate application logins.  I don't want anybody getting the idea
>that they just have to have SQL Management Studio to get in to look at
>their data in the raw.
>
>Steve Erbach
>Neenah, WI