Disconnect Navision users and lock database

Kaetchen

HI,

I would like to do the following:

Notify User to LOGOUT and stop everybody from LOGIN again.

Is there any way to do this in Navision?

Actually I think it would be a great feature to communicate with other users in Navsion with a simple messaging.

The only solution I came up with from stopping people to login again is to use the expiration date in Database Logins, but maybe somebody has a better idea :-k

Thanks,
Kaetchen

David_Singleton

Why do you want them to log out? From the way you are saying this is looks like a regular thing. Yes I know there are rare occasions when you would want this, but I can't see one where you want this as a regular process. Am I missing something?

Savatage

Nav Messenger
<4.0
http://www.mibuso.com/dlinfo.asp?FileID=147
>=4.0
http://www.mibuso.com/forum/viewtopic.php?t=10757

We use www.autocloseidle.com to kill sessions
and I use Remote Desktop Connection to connect tot he server to stop & restart the Nav service just to be sure everyone's out!

Also, An announcement of "Get out of Navision Now or be Fired" over the phone system seems to work too

Kaetchen

I need to do this "optimize' as a monthly job.

It takes quite a while to do this mainly because every time I want to start the job somebody else has logged in again.

I find it hard to believe that the system administrator isn't capable of ending a session and prevent users from logins.

Also, An announcement of "Get out of Navision Now or be Fired" over the phone system seems to work too

Not here... people don't even leave their desks when the fire alarm is going, also I don't have the authority to fire people. They also start to negotiate to do this last printout etc....

How critical is this optimization...? What happens if someone login when the procedure is running?

David_Singleton

Kaetchen wrote:

I need to do this "optimize' as a monthly job.

It takes quite a while to do this mainly because every time I want to start the job somebody else has logged in again.

I find it hard to believe that the system administrator isn't capable of ending a session and prevent users from logins.
...
How critical is this optimization...? What happens if someone login when the procedure is running?

I guess you mean optimizing free space in tables. This process is not important generally, unless you are very low on space in your database. Also depending on your circumstances, it can be disadvantageous to run it, as it can slow you down in some cases.

Secondly why do you need to log users off? Navision is a multiuser system, the worst that will happen is that they will be locked out of the table whilst the optimize is running on that table.

Why don't you sit with your NSC (partner), and get them to explain how this process works,and then evaluate if you really need to be doing it.

Savatage

Yes it locks the person out of the table until the optimizing is done. So you don't need to get them all out.

I asked this many years ago
http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=8033

David_Singleton

Hey and look who answered it

PS 1985 = Just 15 more till Christmas \:D/

Kaetchen

Thanks for the replies.

Our Navision Partner is (was) useless. We have to find a new one.

This forum and the manuals are the only useful source to get information about Navision, thanks again.

Just another question:

How does it work with the backup?

Surely if something would go wrong with the procedure "Optimze Tables", we would need to restore.
But if people work between the backup and the recovery their work would be lost, right?

David_Singleton

Kaetchen wrote:

...

How does it work with the backup?

Surely if something would go wrong with the procedure "Optimze Tables", we would need to restore.
But if people work between the backup and the recovery their work would be lost, right?

Yes of course, but thats how backups are. Its up to you to decide how often to do backups. Basically how much data can you afford to loose? If you can loose a weeks work and have users enter it all over again, then you make backups once per week. If you can afford to loose half a days worth of work, then you back up twice a day.

Again, a backup and recover strategy is something that you sit with your NSC to discuss, plan and design BEFORE you implement your system.

Kaetchen

Our backup runs every night.

In case of a recovery the problem is very often to re-enact what has been done in the meantime and re-enter.

Obviously this procedure (optimize) is not rated highly risky to fall over.

David_Singleton

Kaetchen wrote:

Our backup runs every night.

In case of a recovery the problem is very often to re-enact what has been done in the meantime and re-enter.

Obviously this procedure (optimize) is not rated highly risky to fall over.

Sorry, your original post was not all that clear. Are you saying that you are concerned that if the Optimize routine fails that it would crash the Navision database? If that is your question, then NO. If the optimize fails, the Database does not commit, and so its as though you did nothing.

THE ONLY !!! Function in Navision that if it fails, it takes out the database is the Expand Database function. That is why you always always make a full backup up, and confirm with a test restore before you expand.

Kaetchen

Are you saying that you are concerned that if the Optimize routine fails that it would crash the Navision database?

Yes, this was my main concern as I did not understand why we had to backup before the "optimize".

I took over this job from someone, who did obviously what our previous NSC told him to do and didn't really understand the background.

I don't even see the need for this as we have 40% free space and after what you guys told me performance issues shouldn't relate to this particular "maintenance job".

David_Singleton

OK, so if I get the whole picture, then your procedure was:

1/ Disconnect all users
2/ Create backup
3/ Optimize the database tables
4/ Allow users back in.

Well I can't really speak for you on a procedure designed for your system, but my suggestion would be to discuss it further with your NSC, and tell them that unless they can justify doing this, then I would completely eliminate the whole procedure. I really can't see it as being of any benefit to you. The only thing I see it doing is upsetting the users.

BY the way, why not set up a copy of the database on a test machine, start the optimize, and then just pull the plug mid stream.

Kaetchen

BY the way, why not set up a copy of the database on a test machine, start the optimize, and then just pull the plug mid stream.

This sounds pretty technical, are you sure I'm allowed to do this without a developer license?
Couldn't find an explanation in the help index or the forum.