Today was my first day of class and it was a good day of class. I arrived at the Sybase Training facility this morning, found the class and saw the student list and only three students are registered for the class. Only two of us showed up though. I found this ironic because the person that did not show up was a Sybase employee. Anyway we started class with an overview of what to expect from the class and then we got into some detail.
Module 1 was all about installing a Sybase Server. This is pretty basic stuff. Really you just need to download the software from Sybase for the OS that you are using. If you are using a Unix OS, which I am, then you can open up an xterm session connect to the server and run setup. This will launch the Graphic installer and you are on your way. You will need to answer three questions to get all of the binarys and associated files installed into the $SYBASE directory. After the install is complete you can continue with this wizard to set up the server instance or you can go back later and run srvbuild. This is a better way to do this if you ask me. This way you have one screen to fill out instead of 3 or 4. So that pretty much covers setup.
Module 2 was all about connecting to the DB. ASE supports many connection methods but they also have a preferred way. This is called open server open client. In order for this to work you must have an interfaces file in the $SYBASE directory. This file holds information about the servers. It will have the server name as well as connection info such as protocol and port that the server is listening on. Once you have this set up, this is created during setup, you will be able to use isql to connect to the server once it is running. Now if you would like to connect from a Windows machine then you will need a sql.ini file with the same information in it. The format is a bit different but it has all the same information in it. That is pretty straight forward.
Module 3 was about how to configure the server. In this module we did not talk about what the configuration values should be just how to see them and change them. We really only discussed how to change the config file. Really you have two choices on how to do this. You can edit the file using VI or any other editor or you can log into the database as a System Administrator and use sp_configure to access and make changes to the file. This is the preferred method as about 75% of all configuration options are dynamic and do not require a reboot of the server to take effect. This will also modify the current active config file and make a backup just in case it causes any issues. Nothing much more to this.
Module 4 we got into configuring memory and this is a huge deal. Basically you want to give the data cache as much memory as you possibly can. After you give the OS and any other application on the server the memory that they need make the max memory of the server the rest of the available memory on the server. Then configure all options that will change the memory allocation on the server. Then determine how much you need for the procedure cache and then dump everything else into the data cache.
Looking forward to tomorrow and I will post again.