+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / Split sf Database

Split sf Database

4 posts, 0 answered
  1. Pierre
    Pierre avatar
    433 posts
    Registered:
    16 Feb 2006
    22 Sep 2010
    Link to this post
    Hi Team,

    I need to split my sf database solution preserving security of main database and move some modules inside this external db. Could you teach us and sugest the best pratices to get many databases and connections preserving sf security.

    Thanks, Romi

  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    09 Dec 2016
    22 Sep 2010
    Link to this post
    Hi Pierre,

    Sitefinity is based on Provider Model. Each module has a provider/s. Each provider has a property connectionString where you can set the connection string to your database. If you currently have a single database with data for multiple modules/providers inside it you should use third party tool to extract the data for each provider and migrate it to another database. Then you have to set the connection string to this database for the providers you want to migrate.

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Pierre
    Pierre avatar
    433 posts
    Registered:
    16 Feb 2006
    22 Sep 2010
    Link to this post
    Hi Ivan,

    Thanks Ivan for explains. For modules is clear, use new providers and connections after sf manage all backside for new modules. But could you explain more in the intitials steps. Need to use one complete sf database duplicating a blanc project database as new or other ?.
  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    09 Dec 2016
    23 Sep 2010
    Link to this post
    Hello Pierre,

    You will need two or more Sitefinity databases and migrate the data between them depending on the provider. This could be done with database replication and schema comparison tool. After the providers data is migrated/created all data will go to the database set for each provider you have.

    You could also use load balancing with failover in case one of your severs go down.

    Regards,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Register for webinar
4 posts, 0 answered