-
Ask a question and get free supportUnlock new privileges and see hidden discussionsWin prizes and earn reputation
-
Question of the day ~ How often do you braai?
-
Afristay giveaway.Win a 2-night stay for two people at an establishment of your choice with R1,000 in spending money. Enter here.
Sign up with GoogleSQL Service Accounts help
- Thread starter Solarion
- Start date
DominionZA
Executive Member
- Joined
- May 5, 2005
- Messages
- 8,309
On my dev machine, with the SQL 2014 Developer edition, I leave defaults and select Use Current User where no defaults.
Logged in with admin account.
Logged in with admin account.
Nerfherder
Honorary Master
- Joined
- Apr 21, 2008
- Messages
- 29,703
create a local admin and use that.
Disable RD logon for that admin
Disable RD logon for that admin
Solarion
Honorary Master
- Joined
- Nov 14, 2012
- Messages
- 21,887
Done. I've quickly created a test database and an SSRS report and everything seems to be running ok.
For what its worth, in a test environment / home / non-production it perfectly ok to use SYSTEM auth. Everything will work perfectly.
For production environments, you would create a separate windows authentication account for each service - Engine, SSRS, SSAS and SSIS, SQL agent. Those accounts, whether AD or local should NOT have admin credentials. Any permissions to specific folders etc should be made for each windows auth account individually.
For production environments, you would create a separate windows authentication account for each service - Engine, SSRS, SSAS and SSIS, SQL agent. Those accounts, whether AD or local should NOT have admin credentials. Any permissions to specific folders etc should be made for each windows auth account individually.