By impersonation she potentially means issuing a T-SQL 'EXECUTE AS <login>' instruction, specifying that all subsequent commands issued during that connection/session are executed with the privileges of the login specified.
So presumably from VFP, it would be sending in queries like: 'EXECUTE AS xyz;select * from mytable where account=?' ... and so on. -- Alan Bourke alanpbourke (at) fastmail (dot) fm On Wed, 14 Oct 2015, at 06:04 PM, Kurt Wendt wrote: > Vince, > > One of the things my manager discussed with me is the problems that > others have had. When they get frustrated with trying to setup the proper > access rights. And, then in the end - just say "Hell with it" - and do > the easy way out and assign database owner rights. She is really wary of > doing that - as it seems Not to be the proper answer. > > As for NT Login - do you mean SQL login - instead of doing the Windows > Auth? > > Thanks, > -K- > > -----Original Message----- > From: ProfoxTech [mailto:[email protected]] On Behalf Of Vince > Teachout > Sent: Wednesday, October 14, 2015 12:50 PM > To: [email protected] > Subject: Re: To Impersonate on MS SQL > > On 10/14/2015 12:31 PM, Kurt Wendt wrote: > > We are making changes here at my job - they are switching over to 64-bit > > SQL servers from the 32-bit servers. They've also been implementing > > connections to Databases via the Trusted Connection. But, having to grant > > permissions for various Databases on a per user basis is kinda nuts. So - > > my manager had learned about the "Impersonating" term. So, supposedly you > > have a general account/user - that could be used to access the proper > > databases - and then each specific user Impersonates that general user. She > > heard from others working in VB/.net - about doing the impersonation - but, > > it sounds Code specific. So, that's why she was trying to figure out how to > > do it via FoxPro. But, her searches on the Web was not really turning up > > useful information. > > > > So - hopefully someone here can point us in the right direction. And, yes - > > we are using VFP 9 SP2. > > I've never heard of 'Impersonating,' but it sounds like all she needs is > simply Server authentication. > > 1) Create a SQL Server Login, under the Security tab, give it a PW, and > make it owner of the database in question. > > 2) Have users login with NT Login, instead of Windows authentication. > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/1444898032.2382766.410828337.0f49a...@webmail.messagingengine.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
