Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Implementation of TECH180841

Created: 17 Sep 2012 • Updated: 24 Sep 2012 | 2 comments
be-nugget's picture
This issue has been solved. See solution.

Maybe more of a general question here, but I want to understand a little more about how this SQL stored procedure should be implemented, I know which database to run it against but being a SQL n00b I would like to know if someone could provide more granular steps on how this workaround is to be put in place.  Any instructions by using SQL Management Studio would be appreciated.

Thanks

Comments 2 CommentsJump to latest comment

LCT's picture

Well, I have come across this issue in my production environment. If you really want to know that it actually does in SQL in more details you need to log a case with with Symc Tech Support as they have the problem logged with etrack etc.

On your SQL server, logon and open SQL management Studio, then opon the script to apply the workaround, run it against the affect vault store database(s). MAKE SURE you backup your EV DBs before your run this, there is a reverse (undo) script if you need to reverse (undo) the workaround but a backup would be better.

If you are not sure of what to do in SQL should you be running these scripts? You should get your DBA to do it with the help of Symc Tech Support.

 

SOLUTION
be-nugget's picture

I understand what the script does and I will be speaking to our DBA when he is next available but I wanted to try and understand for myself.  I'll carry on and do some more hunting.