Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Highlighted
Super Contributor.. ellerm Super Contributor..
Super Contributor..
5540 views

Using Same DB for SSC and WebInspect

Jump to solution

Does anyone use the same instance of SQL Server for both SSC and WebInspect.  Currently we use individual instances of SQL Server Express for WI and one central SQL Server instance for SSC.  I'd like to use one SQL Server instance for both if possible.

Thanks,

Mike

Labels (2)
0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: Using Same DB for SSC and WebInspect

Jump to solution

Mike;

Yes!  So long as the Microsoft SQL Server version is supported for both, they may share the same SQL Server.  WebInspect generally needs the Standard or Enterprise edition; weird editions like Personal or Developer will not work.  For SSC 4.20 and WebInspect 10.30, check the Fortify 4.20 (or 4.21) System Requirements document.  For the upcoming 4.30/10.40 release, you would look to the Fortify 4.30 System Requirements document when it becomes available.

  • If you don't have a copy around: 

When sharing a SQL Server, you will end up with separate databases on the database server, such as "ssc_db" and "webinspect_scans_db".  If you have multiple users of WebInspect, each will need to point their WebInspect application to their own scans database, or else there may be collisions or corruption due to simultaneous access to certain areas.  So, for example, you may end up with "webinspectdb_mike" and "webinspectdb_hans" for two co-workers.

WebInspect needs to access its scans database as an Owner, so whatever account is specified for the connection needs to be DBO to that scans database.  The user does not need to be SA or DBA to the database server over all, unless they will need to create the database themselves on-the-fly in the WebInspect dialogs.  In most cases, the DBA will prefer to generate a new, completely blank database, and assign your user account as DBO to it.  Once you connect to that database, WebInspect will build out its tables and other structures.

FYI - Between releases there are often slight schema updates.  The SmartUpdate process will prompt the user to see if it should attempt the schema updates to your scan database automatically.  While this is relatively well-designed, I would always recommend halting at that prompt and ensuring there is a current back-up of the WebInspect scan database in SQL before continuing.  Separately, the same dialog will provide a SQL Query (text) that the user may use out-of-band to update the scans database themselves.  User of SQL Express generally do not have this concern.


-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
0 Likes
3 Replies
Micro Focus Expert
Micro Focus Expert

Re: Using Same DB for SSC and WebInspect

Jump to solution

Mike;

Yes!  So long as the Microsoft SQL Server version is supported for both, they may share the same SQL Server.  WebInspect generally needs the Standard or Enterprise edition; weird editions like Personal or Developer will not work.  For SSC 4.20 and WebInspect 10.30, check the Fortify 4.20 (or 4.21) System Requirements document.  For the upcoming 4.30/10.40 release, you would look to the Fortify 4.30 System Requirements document when it becomes available.

  • If you don't have a copy around: 

When sharing a SQL Server, you will end up with separate databases on the database server, such as "ssc_db" and "webinspect_scans_db".  If you have multiple users of WebInspect, each will need to point their WebInspect application to their own scans database, or else there may be collisions or corruption due to simultaneous access to certain areas.  So, for example, you may end up with "webinspectdb_mike" and "webinspectdb_hans" for two co-workers.

WebInspect needs to access its scans database as an Owner, so whatever account is specified for the connection needs to be DBO to that scans database.  The user does not need to be SA or DBA to the database server over all, unless they will need to create the database themselves on-the-fly in the WebInspect dialogs.  In most cases, the DBA will prefer to generate a new, completely blank database, and assign your user account as DBO to it.  Once you connect to that database, WebInspect will build out its tables and other structures.

FYI - Between releases there are often slight schema updates.  The SmartUpdate process will prompt the user to see if it should attempt the schema updates to your scan database automatically.  While this is relatively well-designed, I would always recommend halting at that prompt and ensuring there is a current back-up of the WebInspect scan database in SQL before continuing.  Separately, the same dialog will provide a SQL Query (text) that the user may use out-of-band to update the scans database themselves.  User of SQL Express generally do not have this concern.


-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
0 Likes
grace.chang Absent Member.
Absent Member.

Re: Using Same DB for SSC and WebInspect

Jump to solution

Was your question answered? If so, please mark the question as correct, so other users will know. Thanks!

0 Likes
Super Contributor.. ellerm Super Contributor..
Super Contributor..

Re: Using Same DB for SSC and WebInspect

Jump to solution

Thanks Hans, for the response.  I completely spaced that I'd asked this question.  At the time I just decided to continue using SQL Server Express but recently started revisiting this.  I appreciate your great answer.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.