Database strategy

Hi,


I am wondering about which project database stategy shall I use (dynamic switching or single database).

Now I have single database and about 10 projects in it, each of the project contains 20 up to 90-100 drawings.
I do not know if it's much or little, but sometimes it seems that I am running into kind of performance issues (quite long promis.e reaction when a database operation is performed).

What will you suggest in that kind of environement? I suppose to add few new projects that year.

If a separate database + dynamic switching is a good option, the conversion will be made automatically or do I have to backup and restore all projects?

Promise 13.57 + SQL 2014.

Best regards,
Wojtek

  • Hi Wojtek.  There is really no formula to say whether you will benefit much from using a Multiple Databases strategy. I would guess that your single database is not that bogged down yet, but you would really need to try Multiple Databases to make that determination. You could take some baseline measurements by timing some of the actions that are slow for you (do the same operation in the same project a few times and time each) create a new project database, move the test project to the new database, and compare.

    I would never discourage backing up projects. But there is a Move To Database option when you right-click a project in Project Manager. In SS7 I would recommend backing up and restoring the project while configured to use the new database yourself, since that is how Move To Database worked but there were certain situations where data could be lost. In SS8 like you are using, the problems have been addressed and the process is streamlined (only the database data is moved, the complete project is not backed up and restored).



  • Hi Matt,

    thank you for that explanation. Finally I have ended up with "Separate database per project" option.
    I have created my brand new project in new database and left all current projects (they're almost finished) in default database. I will see how it works.

    Best regards,
    Wojtek

    --

    Best regards, Wojtek

    SW: Promis.e 08.11.13.96/23.00.00.46

  • Just to share experience: looks like using multiple databases (separate database for each project) speeds up system a bit, but if I want to copy page from one project to another, the projects has to be in the same database.

    That detail have made multiple databases unusable for me.

    Best regards,
    Wojtek

    --

    Best regards, Wojtek

    SW: Promis.e 08.11.13.96/23.00.00.46

  • Wojtek, there is an existing request for the ability to copy projects (easily) between separate project databases: TFS 194279. If you would like to be added to the requestor list for this, please submit a service request. I'm having trouble identifying you in our service request system at the moment.



  • Hi Matt,

    I have submitted a request.
    Is there a list of allTFS accessible somewhere? It might be good to check if somebody requested it, before posting a question at Forum.

    Best regards,
    Wojtek

    --

    Best regards, Wojtek

    SW: Promis.e 08.11.13.96/23.00.00.46