Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Service Account User for SQL Server
ta5
Member Posts: 1,164
Hello experts
As we all know sql server service can run under a domain user or a built in user (local system, etc.). I'm interested in your opinion about what do you think about this issue. Do you ever use "Local System"?
Thanks in advance.
Thomas
As we all know sql server service can run under a domain user or a built in user (local system, etc.). I'm interested in your opinion about what do you think about this issue. Do you ever use "Local System"?
Thanks in advance.
Thomas
0
Answers
You should always use a dedicated domain account for the SQL Server services. This enables you to specify the security rights, e.g. if the SQL Server shoould access remote drives or servers (Log Shipping etc.)..
This SQL Service account shoud be (IMHO) assigned to these groups:
- Local Administrators
- Lock Pages in Memory (must have with 32bit systems using AWE)
- Perform Volume Maintenance Tasks
Cheers,
Jörg
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool