595
I have a client who just switched over from SQL authentication to Windows authentication. They had been replicating the SQL databases over to another server as part of their DR plan. Now that we've switched authentication methods their IT dept is saying they can no longer replicate them because there is no primary key column any longer. Does windows authentication remove this?
Cherie
*This post is locked for comments
Yes Eric, that is perfect! Thanks so much.
Check out whether they have permission issues on the SQL side. As odd as it seems, a regular Windows authenticated SL user does *not* have read access to the SQL tables, even though they can use the SL client application with no problem at all. This is so by design.
SL uses a not so well known SQL feature called Application Role, so an authenticated user can access the data only through the SL client. This prevents tampering the database through Excel, Infopath or any tool easily available.
This also prevents running SQL scripts on the side, like backup, index rebuild or replication tasks.
The thing with this approach is that the TI dept may misdiagnose a permission issue saying "I know the permissions are right, since SL works".
In order to run maintenance SQL script, you should setup custom SQL permissions, or use the sysadmin role.
Authentication has nothing to do with table structure. The Replication would have to be re-built and re-established with Windows Authentication in mind.
Or we are missing some key facts.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (