Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Query in SQL Database Logins
chandrurec
Member Posts: 560
Hi all,
I have created logins first in sql generic login , then I am going to restore the database and tag the database login to the newly restored database. Is it adcisable to create the login first then tag it to the database or it will not work.
Thanks in advance.
Regards,
chandru.
I have created logins first in sql generic login , then I am going to restore the database and tag the database login to the newly restored database. Is it adcisable to create the login first then tag it to the database or it will not work.
Thanks in advance.
Regards,
chandru.
0
Comments
When you restore the database the logons are only restored to that specific databases security section. e.g if you have no accounts specified in SQL - Security when you restore a database you will STILL have no logons after the database is restored. If you then try to create the logon and link it to the database it will fail saying that the SQL user already exists within the database (might also get a schema error in some cases). If i remember correctly, creating the users within the SQL security before restoring the database should be fine but a built in SQL stored proceedure needs to be run to tie the login ID's together, i think its called user_login_change? although i may be wrong on the naming.