[dba-SQLServer] [dba-VB] SQL Server security

Thanks I'm going to be adding some new stuff soon

On 1/5/11, Jim Lawrence <jlawrenc1 at shaw.ca> wrote:
> A nice new blog you have there fransico.
>
> Jim
>
>
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco
> Tapia
> Sent: Wednesday, January 05, 2011 11:41 AM
> To: Discussion concerning Visual Basic and related programming issues.
> Cc: Sqlserver-Dba; Access Developers discussion and problem solving
> Subject: Re: [dba-SQLServer] [dba-VB] SQL Server security
>
> -Francisco
> http://bit.ly/sqlthis   | Tsql and More...
>
>
>
>
> On Wed, Jan 5, 2011 at 10:00 AM, jwcolby <jwcolby at colbyconsulting.com>wrote:
>>
>> I do not have experience in a transactional database using SQL Server, but
>> I am thinking that SQL Server express 2005 will not have an issue keeping
> up
>> with this kind of usage - 25 users adding records to this table all day
>> without causing locking issues like I am seeing now.
>>
>
> It's been a while since I did a conversion, I don't remember if you need to
> make all your fields varchar or nvarchar, but that's the gist. I remember
> also going unbound to simplify the data entry process, but ymmv with that
> piece of advise.  We have SQL Server running in the backend for many of our
> transactional systems and we have > than 25 users all w/o locking problems.
>
> My issue at this point is that they use a network logon and force the users
>> to change their password every 30 days.  Is SQL Server going to use that
>> same network username / password database or does it use a list of
> usernames
>> / passwords physically on the server itself?  IOW will Windows
>> authentication work or will I need to go to SQL Server username /
> password?
>
>
> Windows Authentication will work just fine.  To simplify the user to server
> problem, you'd want the network admin to add your users who have access to
> the application to a specific domain group... then just give access to the
> domain group.  You can even put security around who has access to what based
> on domain group, works a treat.  If you have too much difficulty with that
> you can always fall back to sql authentication, but I always prefer windows
> authentication except for the web apps we have...
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>

-- 
Sent from my mobile device

-Francisco
http://bit.ly/sqlthis   | Tsql and More...