Uncategorized

Handling Security With SQL Server

Featured Article(s)
Create an ADO function by stored procedure name
In this article I would like to present and describe the SQL script which produces front-end ADO called a function by a stored procedure name. For both VB.NET and C#.

Handling Security With SQL Server
How do you approach security for SQL Server? It’s a tad easier question if you remove web applications from the mix. Typically people will use integrated security and profiles and policies to make sure best practices are enforced… If you’re not doing this, how do you approach this? I do still run into installations using SQL Server-only security – and mixed security is certainly a norm given the number of applications and such that require SQL Server-base access rights.

But, throw in web-based applications – then how do you approach this? I think you’re pretty much forced to either have a pretty solid user management approach to your web development or you’re faced with SQL Server-based security. Even with SQL Server-based security, you still need to have a thoughtful approach to this – you can’t have developers using developer-based credentials for deployed applications, and there should be a password refresh interval for applications. Typically though, it’s more of a "Deploy it and don’t touch it, it works…" approach.

How do you handle and manage your security?

Drop me a note, let me know.

Featured White Paper(s)
SharePoint: How It’s Leveraged and How It Works
This white paper will first examine how users, managers, and network administrators view and utilize SharePoint and it will l… (read more)

SharePoint Customization Best Practices
In this paper, we will tackle a subject that has raised many questions and an equally large number of answers. How do I custo… (read more)