BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
vkrishna
Quartz | Level 8

Hi,

 

Can we upgrade the SAS server to new maintenance release by applying hot fixes instead of SAS software depot?

It works?

 

Windows server 2012 R2, single machine

Office analytics

 

1 ACCEPTED SOLUTION

Accepted Solutions
JuanS_OCS
Amethyst | Level 16

Hello @vkrishna,

 

I think @SASKiwi is following up greatly your questions.

 

Just a couple of additions to his guide:

 

  • For software updates, please check the guide, always very useful http://documentation.sas.com/?docsetId=whatsdiff&docsetTarget=titlepage.htm&docsetVersion=9.4&locale...
  • If you are concerned about loosing settings:
    • Customisations to compute must go to _usermods files. If any change is out of those files, you should keep a copy of the non-usermods files.
    • Also, if you have web applications and since you will need to rebuild and redeploy them, every customisation to web applications (such as timeouts or themes) should be copied and restored after the maintenance, by you.
    • You should always make a good backup of the system before any big change, as a maintenance level application.

View solution in original post

5 REPLIES 5
SASKiwi
PROC Star

Unfortunately not. Maintenance releases include new functionality and hence new software.

vkrishna
Quartz | Level 8

Thanks @SASKiwi. If we upgrade to new maintenance release it will change the system options? like memsize. 

SASKiwi
PROC Star

It's possible, but if you have applied your own modifications in the "user mods" config files then these won't be overwritten.

JuanS_OCS
Amethyst | Level 16

Hello @vkrishna,

 

I think @SASKiwi is following up greatly your questions.

 

Just a couple of additions to his guide:

 

  • For software updates, please check the guide, always very useful http://documentation.sas.com/?docsetId=whatsdiff&docsetTarget=titlepage.htm&docsetVersion=9.4&locale...
  • If you are concerned about loosing settings:
    • Customisations to compute must go to _usermods files. If any change is out of those files, you should keep a copy of the non-usermods files.
    • Also, if you have web applications and since you will need to rebuild and redeploy them, every customisation to web applications (such as timeouts or themes) should be copied and restored after the maintenance, by you.
    • You should always make a good backup of the system before any big change, as a maintenance level application.
vkrishna
Quartz | Level 8

 

@JuanS_OCS,

 

You mentioned that 

  • Also, if you have web applications and since you will need to rebuild and redeploy them, every customisation to web applications (such as timeouts or themes) should be copied and restored after the maintenance, by you.

Yes, we have applications.

Is it required or mandatory to rebuild and redeploy the web applications after upgrade? 

I read that when we update SAS will rebuild, redeploy and restart the we applications.

 

 

Thanks,

V

 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 2555 views
  • 9 likes
  • 3 in conversation