2.2.1 How to Start ASE on Remote NT Servers
2.2.2 How to Configure More than 2G bytes of Memory for ASE on NT
Currently, there is no method of starting ASE on a remote NT server using Sybase Central. So how do you get ASE running on an NT server located in one city when you are currently located in another. OK, OK, so flying there is an option, but let's try to stay within the realms of practicality <g>.
One option is to buy a good telnet server and telnet onto the box and then start it using the "RUN_<server>.BAT" file. This works, but depending on the telnet server can be a little troublesome. NT does not have such a nice set of commands as Unix, so there is no "startserver" to run the server in the background. This means that the telnet window that you use to start the server may have to stay open for the lifetime of the server. This means that the health of ASE is now dependent upon two machines not crashing. As I say, your mileage may vary, but I have certainly found this to be the case with at least one telnet server.
Another option is to use SRVMGR.EXE from the Windows NT resource kit. Roughly you issue
srvmgr \\SERVER-TO-BE-MANAGED
(obviously replacing SERVER-TO-BE-MANAGED with the name of the server you wish to start ASE on!)
Select the "Services" option, and start ASE as if you were in the "Services" applet on a local NT server.
Yet another option is to install PC Anywhere or VNC on both machines and use one of these tools to remotely control the system. (VNC is a very good version of PC Anywhere, except that the clients and servers run on NT, Unix, Linux; the source code is available and it is free (in both senses of the word)!)
If anyone knows of any better methods, please let me know and I will add them to this section. Thanks.
The following was posted on news://forums.sybase.com/sybase.public.ase.nt , taken directly from a Sybase SPS case notes.
If you are using NT server enterprise, or Windows 2000 Advanced Server, you may be able to get up to 3gig:
Here is what you need to do in order to configure greater than 2GB memory for ASE on NT:
Step 1: Make a backup copy of sqlsrvr.exe in the sybase bin directory
Step 2: Verify the current settings of sqlsrvr.exe using imagecfg.exe:
imagecfg sqlsrvr.exe sqlsrvr.exe contains the following configuration information: Subsystem Version of 4.0 Stack Reserve Size: 0x20000 Stack Commit Size: 0x4
Step 3: Use imagecfg to switch on large addressing using the -l (lowercase L) switch:
imagecfg -l sqlsrvr.exe sqlsrvr.exe contains the following configuration information: Subsystem Version of 4.0 Stack Reserve Size: 0x20000 Stack Commit Size: 0x4 sqlsrvr.exe updated with the following configuration information: Subsystem Version of 4.0 Image can handle large (>2GB) addresses Stack Reserve Size: 0x20000 Stack Commit Size: 0x4
Step 4: verify ASE is able to start
Step 5: The NT machine must be booted with the /3GB flag and must have sufficient paging file space (e.g., if you want ASE to access 3G of memory then the paging file must be at least that size)
Step 6: increase total memory to say 2.2 gb (anything > 2gb)
Step 7: increase starting virtual memory address to 23662592 decimal (which is 1691000 hex) as shown:
sp_configure 'shared memory starting address', 23662592
Step 8: restart server
Step 9: test to connect a lot of users (more than 240)