Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
crazycat503
Starting Member
16 Posts |
 Posted - 2013-01-08 : 03:39:02
|
| Hi,CUrrently, we developed a db that uses windows mode with integrated security. Now, the application [.net] will be deployed to many clients who run their own usernames that are not registered in the sql server. What's more is that they can have their own passwords. Hence, user's cant be connected to the database server at all.AN idea that came into mind was to create a windows service that would then be used to connect to sql server 2008. THe idea is it wouldn't matter who is currently logged in as long as the service auto-starts. I know how to create the service but not how to connect to sql server thru it. Is the idea good and credible? ANy one have experience wit it? HOw about connecting from dot.net thru it? NOte that the sql server 2008 got one instance only.Please share your insight and advice on it. Thank you all.All guys! |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2013-01-08 : 04:04:24
|
| You can use a single user in the app to connect to the server/database then it doesn't matter who the users are.You might want to add something to the app so you can tell who the user is though.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2013-01-08 : 04:17:17
|
| why not create an application role and just map required users from app to it? app always connectes to sql server using the application role------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
|
|
|
SQL SERVER Login Problems