January 30, 2008 at 8:05 pm
I want to create an application which can work with SQL Server 2005/2008 using Windows Authentication or SQL Authenticaton.
If the application is configured to use SQL Authentication (SQL Server is
configured to use SQL Server and Windows Authentication mode), the
application will create a SQL Login which has enough permission to create databases used by the application and that SQL Login will also be used by the application to access the databases. In order to create the SQL Login, the application will ask for a login which has enough permissions to create the SQL login needed by the application.
If the application is configured to use Windows Authentication, what should the application do? For sure, the application will not create Windows groups/users in Active Directory. Should the application add Windows groups/users as SQL Logins? Is there any guideline in creating application to access SQL Server using Windows Authentication from having no user databases in SQL Server to having user databases in SQL Server?
I'm not sure how real application handle this. I'm thinking that an application may require users to setup one or more special windows group/user in AD to be used by it.
The applicaton that I'm dealing with will need to able to create additional databases so creating database is not just a one time thing.
February 1, 2008 at 2:41 pm
I'm not sure you can do all you want but you can create login and database with smo in c#.
http://msdn2.microsoft.com/en-us/library/ms162557.aspx
French Geek.
http://blog.developpez.com/ylarvor
I work my english 🙂
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply