I'm confused by MS installation notes on SQL for NAV. They say to install SQL with Windows Authentication. From early NAV installation documentation, NAV requirement was always to have at least a single SUPER user in database logins. Has that requirement gone? I'm not seeing anything in docs.
help set me straight?
thanks! :oops:
0
Comments
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
RIS Plus, LLC
MVP - Business Apps
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I was talking from the SQL point of view. I don't disagree with you from the NAV point of view. As I said, I tend to use "mixed mode". We may find that this "NAV point of view" changes when the native database goes away.
Can you elaborate on this? I can't think of anything that requires database logins, except access from a system that can't support Windows Authentication. (but it is early and I haven't had my coffee). And yes, there's the part about moving it back to native, but that's no different then moving a SQL database to another system.
Have you ever heard of that happening though?
I'm referring to the situation where a consultant may take a backup and restore to a local DB on their laptop. Yes, I know you can just use SQL Developer Edition, but I still see many consultants (and some developers) that are more "comfortable" with a local native database.
I actually have tended to use "mixed mode" in the vast majority of my SQL installations over the years (this includes non-NAV systems). I would tend to use "Windows Authentication" only if there was a specific requirement for it. The one thing that "mixed mode" gave me was a more flexible remote access enviroment (talking non-NAV here).
As you described. I mean you can use DB logins, thus use this "functionality" in situations when AD is not available, or users are using same Windows profile, or you need to have remote access from your notebook when you are on site etc. It means there is area which cannot be used when Windows only authentication is used. It looks like just a simple feature, but in many cases it helps like some big addon... 8)
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Agreed. As you know, a vendor's preferred (recommended) configuration isn't always the best configuration in the real-world. (But it can be helpful to know the vendor's view when it comes to taking exams.)
The first is testing security. Its nice to be able to create Database Login the same as the users windows login to test issues with security.
Second is when I need to log in as me from another users computer. DB logins make that much easier to find problems.
As a personal rule I simply don't allow this. I have seen too many cases where a subtle difference between test and live environments has caused big problems. So the consultants use the same as live.
Thinking further though LS Retail is one case that does fit your scenario.
Incidently enhanced mode gives us the most problems and I do not like it.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!