This is a followup to Solution Id: S-022257 . That solutionwould not work for us because we needed to add another vault and wealready had a vault in production live and it good not be takindown. So we are publishing our fix.
We tried to add feedback to there system but it wouldn't let uscomment on solution s-022257.
READ KB s-022257 first so you are aware of the issue and can seeSolids fix.
This solution would work for my clinet if we could shutdown ourother vault but that was not a option. We had to get creative andfind a better solution and here is what we came up with and itworked.
We had a production vault and we wanted to create a test vault.When we did we got the error could not import defaults. With theinfo from this kb we made our own solution. And here it is.
Create new vault use sa password for creation and use defaults foradmin and as soon as you click finish and the database is rightbefore the importing starts(1-2 seconds best if ran by 2 machinesand 2 people one creating on pdm and one logged into sql managementstudio to run sql query) we ran a sql script on our sql server toadd our default sql user for the other vault db to our newlycreated vault db. The script creates a new user under that new dband adds db_owner role to that user. In our system it worked greatand no down time on the prod vault.
You must change NEWDBNAME to your name and also pdmwe to yourpdmwelogin sql user account
Also rember you have seconds to run this after you start it must bedone as soon as the database is created. This soultion is reallyonly for people wanting to build a second vault and can't shutdownthere other vault during so. Otherwise use this KB to do a singlevault.
******************************************************************
USE [NEWDBNAME]
GO
CREATE USER [pdmwe] FOR LOGIN [pdmwe] WITH DEFAULT_SCHEMA=[dbo]
GO
sp_addrolemember 'db_owner','pdmwe'
Feel free to contact me for help and or comments atjames@jcdataconsulting.comSolidworksGeneral
We tried to add feedback to there system but it wouldn't let uscomment on solution s-022257.
READ KB s-022257 first so you are aware of the issue and can seeSolids fix.
This solution would work for my clinet if we could shutdown ourother vault but that was not a option. We had to get creative andfind a better solution and here is what we came up with and itworked.
We had a production vault and we wanted to create a test vault.When we did we got the error could not import defaults. With theinfo from this kb we made our own solution. And here it is.
Create new vault use sa password for creation and use defaults foradmin and as soon as you click finish and the database is rightbefore the importing starts(1-2 seconds best if ran by 2 machinesand 2 people one creating on pdm and one logged into sql managementstudio to run sql query) we ran a sql script on our sql server toadd our default sql user for the other vault db to our newlycreated vault db. The script creates a new user under that new dband adds db_owner role to that user. In our system it worked greatand no down time on the prod vault.
You must change NEWDBNAME to your name and also pdmwe to yourpdmwelogin sql user account
Also rember you have seconds to run this after you start it must bedone as soon as the database is created. This soultion is reallyonly for people wanting to build a second vault and can't shutdownthere other vault during so. Otherwise use this KB to do a singlevault.
******************************************************************
USE [NEWDBNAME]
GO
CREATE USER [pdmwe] FOR LOGIN [pdmwe] WITH DEFAULT_SCHEMA=[dbo]
GO
sp_addrolemember 'db_owner','pdmwe'
Feel free to contact me for help and or comments atjames@jcdataconsulting.comSolidworksGeneral
