4 replies to this topic

[Ross Bevin]

Hi there,

We migrated our application to a Windows/SQL Server environment from Unix/ProISAM back in 2003. Since that time we have always rebooted the server every night; the ProIV kernel and SQL Server reside on the same physical server. We were advised to do this because of purported memory leak issues in Windows 2003 Server at the time.

Next month we will be purchasing a new server and migrating our environment to all 64 bit versions of Windows 2008 R2 Enterprise Server, SQL Server 2008 R2 Standard and ProIV 7.1. We like to run the ProIV kernel on the same server as SQL because there is a gain in performance of around 25%. Since our non ProIV application development team also uses SQL Server on our server, they are giving us grief on the nightly reboot because the SQL cache is cleared. They would prefer us not to reboot. Keep in mind though that our application is the dominant one and takes precedence over all others.

I have 2 questions:

1. Based on the new 64 bit environment above, should we or should we not be rebooting the server nightly?

2. Or, are we better off running two virtual servers on this new physical server; one for ProIV and another for SQL Server? I'm assuming I would still retain my 25% performance gain because both are on the same physical server. We could then reboot the ProIV server nightly if this is the best option.

Regards
Ross

[Wim Soutendijk]

Hi Ross,

We never reboot the servers. the sql server and proiv server are separate (64 bit) servers. The only thing we do is a restart of the proiv services every night. That clears away any processes left by users just turning their PC off, and clears the memory usage. SQL doesn't need a restart or reboot.

wim

[Ross Bevin]

Hi Wim,


Thanks for your reply. We have many users who don't log off correctly so restarting the kernel without rebooting is a good idea.

Thanks
Ross

[George Macken]

Hi Ross

"We have many users who don't log off correctly so restarting the kernel without rebooting is a good idea."

We have also encountered this problem of users not logging off, it was a very regular occurrence when we exposed the system to (wan, stunnel, vpn, etc), we implmented usage @TIMEOUT to log-out users after a period of inactivity and this made a big difference in reducing the occurrences.
Platform win2003, pro-iv 5.5 and oracle 9i, generally servers are not re-booted, occasionally the pro-iv service is stop/started to clear any rogue sessions/users.

Rgds

George

http://www.proivrc.c...h__1#entry19180

[Ross Bevin]

Hi George,

Thanks for your reply. Yes, we use to use @TIMEOUT but law abiding users didn't like being logged off during the day just because they had been idle for a few hours. I'm going to take Wim's advice and reboot the ProIV services each night to clear rogue sessions. Just so that it's noted here in this post, it was pointed out to me by Northgate that in order to flush ProIV memory both the ProIV V7 Server & ProIV V7 Windows Kernel Server services need to be stopped first, then restart both.

Regards
Ross


PS: I'm going to create new post to mention something important about the ProIV V7 Windows Kernel Server service.