![]() (But it would not be an SQL User - SQL users only have permission inside SQL Server. ![]() This means that for access to file shares on other computer, the access will be through the machine account DOMAIN\MACHINE$.Īnd then you have things that runs under Agent - here access may be for the service account for Agent, and this may be the account that needs permission to the repldata folder. In many cases, the service account is local to the machine, for instance NT Service\MSSQLSERVER. If you are logged in with SQL authentication, access will always be through the service account. When it comes permissions in Windows, it is a little tricky, because sometimes SQL Server attempts to impersonate you, and sometimes access is always through the the service account that SQL Server is running under. If your Windows login is a member of the sysadmin role, you can do anything that sa can do. When it comes to what you can do inside SQL Server, what matters are your permissions. In parallel and for each server, query the SQL information (BuildNumber. I cannot answer the specifics about the repldata folder, since I don't work a lot with replication. The way it works is as follows: Query table Inventory in database Inventory, which contains one entry for each instance with the details: ServerName, InstanceName, Version, BuildNumber, ServicePack, OSVersion, OSBuildNumber, OSServicePack and DatetimeLastUpdate. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. If you have extra questions about this answer, please click "Comment". If the answer is the right solution, please click " Accept Answer" and kindly upvote it. Sa is highest privilege acocunt in SQL Server, it is a member of the sysadmin fixed server role and has all the permissions that exsit inside SQL Server, it is normal if some Windows Auth has permission errors, you must check your account has the appropriate permissions, unless it is a member of the sysadmin role Grant the Snapshot Agent wrire permission to the folder, and ensure that read permission is granted only to the Windows account that the Merge Agent or Distribution agent users when accessing the folder. You need create a separate Windows account on the local server the some related agents. You can refer to this: Tutorial: Prepare SQL Server for replication (publisher, distributor, subscriber) You can’t be 100 sure you’ve listed all sql servers on the network unless all are configured to work on default 1434 port. This helps handle heavy workload with ease.After sharing the repldata folder what SQL User/Creds need to have permissions to the repldata folder for merge replication to work properly.
0 Comments
Leave a Reply. |