Logon Performance Via windows Authentication

surajv

From 4.0 SP1 originally we experienced a delay on logon approx 30-40 sec. Then while on the 4.0 I applied a hofix which essentially became 4.0 SP2 and everyone noticed a much better performance at logon using Windows Authentication, the logon time reduced to fraction of second. Now that we are testing the 5.0 SP1 we have again seeing a performance issue which is taking a user approximately 30-40 seconds to logon.

Does anyone have any idea on how to make this any better?

ppavuk

Where is the point to migrate to old versions?
Why not to try 2009 R2?

BTW, never had any problem with logon time on any version of NAV. Must be IT issue.

Slawek_Guzek

Go to File -> Database -> Alter, select Advanced tab, check Security Model setting. I bet it is Enhanced now.

Change it to Standard.

ppavuk

I had a lot of customers who use enhanced. Never had any problem with it.

kriki

ppavuk wrote:

I had a lot of customers who use enhanced. Never had any problem with it.

And all the users had dbowner in SQL? Or were sysadmin in SQL?

ppavuk

No, just users, no dbo.

surajv

I had a customer who was using enhanced security and wanted to change to standard as importing objects were taking so long.

So when the customer was carry out the task after an hour he concluded it crashed and end tasked. He asked me how long should this process take i said depends on the DB size and advised him to try on test database and surprising everything was done within 10 minutes.

Has anyone experienced a crash or taken over one hour to switch from enchancd to standard security?

ppavuk

This can take the same or even more time as permissions synchronisation. Basically, when you changing security model to simple system will reset right on SQL tables for each user. This can take a while.

kriki

But to do it, you need to put the DB in single-user mode.
If your database is opened by something else, your session remains blocked, showing nothing, until it can put the single-user mode. This can seem it takes a very long time to do the change but in reality your session is just waiting....

The best is to control with sp_who2 in SSMS to see who is blocking your session and killing that session if needed.

surajv

Yes session by NAS maybe causing the issue. I have recommended to stop NAS and try again i think this must be the cause.

Thanks