Over the past few weeks I must have done about half a dozen SAS® 9.3 installations and deployments (mainly Linux 64-bit server and Windows 7 32-bit client). Not because of any problems really, just trying out a variety of options. My experiences have been very good. I must say the SAS installation and migration process is getting really streamlined now. Refreshingly easy actually. I even repeated a couple of installs because it would be easier to change some items during install than manually modify them in the new installation (something I wouldn’t have done with SAS 9.1.3). Of course, whilst SAS installations/migrations are getting more straightforward, I’d still recommend getting SAS Professional Services or one of the SAS partners to help – being businesses that install, migrate and configure SAS software on a daily basis they are very efficient and have extensive support resources at their disposal. I can’t imagine how it could be cost effective for SAS customers to acquire those skills when it’s something they might only do once or twice every few years.
My first impressions of SAS 9.3 have been very good. The installs and migrations went very smoothly. At Metacoda our installations are based on standard deployment plans and used for development and testing of our Metacoda Security Plug-ins software. Whilst our SAS installations are not very complex, we do have deployments with lots of carefully constructed, weird and wacky metadata security configurations. Deployments that, were you to see them in real-life, would have you wondering what was that administrator thinking! They are perfect for developing and testing our Metacoda Security Plug-ins software though! With SAS Migration Utility (SMU) based migrations our Lev1 and Lev2 security metadata came over perfectly from SAS 9.2 to SAS 9.3. We also did a clean empty Lev3 deployment too. I’m hoping that in future, with virtual folders in SAS 9.3, and the ability to easily export ACTs, users, groups, and roles, we could switch to using package exports and imports to promote this security metadata from SAS 9.3 to SAS 9.4 and beyond.
From our perspective SAS 9.3 seems to be very compatible with SAS 9.2 too. We were very pleasantly surprised to find our Metacoda Security Plug-ins ran in SAS Management Console 9.3 almost without change. A few minor modifications based on underlying changes in the SAS metadata model (the Login object changed its parent from SecondaryType to PrimaryType) and now we are running our plug-ins in SAS Management Console 9.3. We are so happy with it that our V2 release currently in beta will support both SAS 9.2 and SAS 9.3 when it goes live soon.
I have heard some people say they are hesitant about upgrading from SAS 9.2 to SAS 9.3 based on their experiences with SAS 9.1.3 to SAS 9.2. Personally I remember the move from SAS 9.1.3 to SAS 9.2 seemed more like a major version upgrade than a point release. I always wondered why SAS 9.2 was not SAS 10 ;). In contrast, the move from SAS 9.2 to SAS 9.3 does feel more like a point release upgrade to me. Whilst there may have been lots of improvements under the covers and a several welcome new additions, as a SAS platform administrator it still feels very similar to SAS 9.2. No huge learning curve and the users get to use almost the same clients they were using with SAS 9.2 M3 too.
I’ll certainly be recommending upgrades from SAS 9.2 to SAS 9.3 and for those currently on 9.1.3 it makes much more sense to me to go straight to 9.3 – the direct migration path is supported and why do two migrations and two rounds of testing when you can do one?
Some of the main administration oriented improvements I’m keen to look at in detail include:
- Integrated scheduled SAS metadata hot backups. Now everyone gets scheduled metadata backups out of the box with no down time for the metadata server.
- Easy SAS metadata restores with roll-forward recovery.
- SAS Management Console virtual folders for exporting and importing users, groups, ACTs etc.
- New SAS Management Console Search tab.
- Enhancements to pre-assigned libraries.
- IWA support for UNIX servers.
Keep an eye out for a few more posts from me on SAS 9.3. I’m hoping I get some time to document some of my 9.3 experiences as I investigate further.
Update 30Aug2011: Andy Ratcliffe mentions this post in his blog post NOTE: Upgrading to SAS 9.3 where he also makes some good recommendations about obtainining pre-installation architecture plans and post-installation implementation documentation.
Hi Paul.
I heard that you can’t install over the top of 9.2 (like M3 update), ie. seperate install of 9.3 is required, Is this the case? If so how does it get around using the same ports in the configs etc on the same machine…
Barry
Hi Barry,
Thanks for your comment.
That’s right. I imagine that most would want to run SAS 9.2 and SAS 9.3 side by side for the duration of migration and testing anyway. As far as machines/ports go, there are a few options which include:
1) Same machines + same ports: whilst possible it’s not a very realistic option as it means you have to shut the entire SAS 9.2 platform down to start the SAS 9.3 platform and vice-versa (unless you try to go down the route of having multi-homed servers and bind them to different IP addresses).
2) Same machines + different ports: enables you have have SAS 9.2 and SAS 9.3 running side by side but they have to be on different port banks. If you have SAS 9.2 deployments as Lev1, Lev2 and Lev3 you could have SAS 9.3 deployments as Lev4, Lev5 and Lev6 for example. Of course, the machines would have to have enough resources to handle the additional deployments and you would have to use the same architecture.
3) Different machines + same ports: the different machines could be physical or virtual. This can avoid consuming the resources from existing SAS 9.2 deployments and also allows for a change in architecture if desired such as 32-bit to 64-bit or a change/upgrade in server operating system.
All of these have their pros and cons and SAS Institute (or partner) could advise on these and the architecture choices as appropriate for your environment. I’m sure SAS Institute would also let you know if there are any licensing implications for any of these choices in your environment if using different physical/virtual machines for example.
The following resources are handy if you want to find out more:
* SAS 9.3 Intelligence Platform: Installation and Configuration Guide: http://support.sas.com/documentation/cdl/en/biig/62611/PDF/default/biig.pdf
* SAS 9.3 Intelligence Platform: Migration Guide: http://support.sas.com/documentation/cdl/en/bimig/62613/PDF/default/bimig.pdf
Cheers
Paul
Hi Paul,
Need your help – Please if you can suggest me something here:
It’s for a migration to a new installation 9.2 to 9.4:
Looking on this site – http://support.sas.com/documentation/cdl/en/bisag/66813/HTML/default/viewer.htm#n1f9181cn1d545n1odu6hkrrcee4.htm#n1s4gwfo1t995dn1a96eghgforn0
About halfway down, under Promoting Security Objects and Server Objects it has this paragraph;
You can promote security objects (users, user groups, roles, and access control templates) and all of the server types that can be registered in metadata. The promotion of these objects can be useful when you are creating or refreshing a SAS environment that mirrors an existing environment. For example, you can use this feature to help create a test environment that mirrors your production environment and to refresh the test environment as needed. Or you might choose to create server or security objects in a test environment and then promote the objects to your production environment after the objects have been tested.
Does this work?
There is much more than 12 users. The ACT’s are very hard to read because the lag time using X windows can take 5 minutes or more to refresh a page so I am looking for a simpler way to move them.
As far I know, The ACT’s will not migrate and I cannot figure out how to get a list of them.
The ability export and import security objects was introduced in SAS 9.3, so unfortunately you can’t use this method to export ACTs from SAS 9.2 to import into a SAS 9.4 installation. You will need to manually recreate the ACTs in SAS 9.4 to match what you have in SAS 9.2 – hopefully you don’t have too many :) Our Metacoda Security Plug-ins ACT Reviewer provides a great way to review ACTs and also export HTML reports about them – you may find this useful when recreating your SAS 9.2 ACTs in SAS 9.4
Are you using X tunnelled over SSH? I too have found significantly delays in using SAS Management Console via X over SSH. You may find it quicker to install SAS Management Console on a Windows machine (or virtual machine) and connect to your remote Unix server. Alternatively remote desktop into a Windows machine which has SAS Management Console installed and is closer to the Unix server.