<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects</link><pubDate>Fri, 03 Apr 2020 10:51:07 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Satish Saptasagar</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Current Revision posted to OpenUtilities Wiki by Satish Saptasagar on 4/3/2020 10:51:07 AM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.140&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Project Management&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Backup and Restore Project&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving Promis.e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance. Promis.e and Bentley Substation require a consistent 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), [[Backup Project|backup]] all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;[[Restore Project|Restore]] the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and involves backing up and restoring the SQL project database(s). It should be performed while there are no users using Promis.e/Bentley Substation. &lt;strong&gt;SQL Server Management Studio&lt;/strong&gt; is included with some Promis.e and Bentley Substation packages, otherwise see [[Install SQL Server Management Studio]]. SQL Server Management Studio can be installed on a machine other than the source and destination servers, but you will need access to the servers&amp;#39; hard drives in order to retrieve and copy the database backup file.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;[[Backup Project|Backup the critical projects using Project Manager]] while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;Backup the SQL project database(s) on the source server using SQL Server Management Studio&lt;/a&gt;.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; Determine the database to backup and the server that hosts it by looking at the [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt; dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders now, just in case.&amp;nbsp; This way the backup of the project folders will be synchronized with the backup of the database.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx" rel="noopener noreferrer" target="_blank"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used to connect to the destination SQL Server and associate the login(s) with the database.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users, see the [[5824|Creating an SQL Server Login]] article. The script in the article should be executed for each project database being moved.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the &lt;strong&gt;Project Database&lt;/strong&gt; area of the [[Setup]] dialog of each workstation, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Ensure the projects affected by the move are accessible to users.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database/server.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database (.MDF) and transaction log files (.LDF) can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx" rel="noopener noreferrer" target="_blank"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server. SQL Server Management Studio is still required for this task. Note: A database named &amp;quot;promise&amp;quot; would have two related files: promise.mdf and promise_log.ldf. Both are required. These files are typically found in the &lt;a href="/products/electrical___instrumentation/w/electrical_and_instrumentation__wiki/6619/finding-the-sql-data-folder" rel="noopener noreferrer" target="_blank"&gt;SQL Server DATA folder&lt;/a&gt;.&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Backup Project]]&lt;/p&gt;
&lt;p&gt;[[Restore Project]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Finding the SQL Data folder]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/p&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Backup and Restore Project, Database Platform Support, promis.e, Administration, SQL Server, how to, Bentley Substation, en, Project Management&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/25</link><pubDate>Thu, 02 Nov 2017 20:14:45 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 25 posted to OpenUtilities Wiki by Matt_P on 11/2/2017 8:14:45 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.140&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Project Management&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Backup and Restore Project&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving Promis.e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance. Promis.e and Bentley Substation require a consistent 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), [[Backup Project|backup]] all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;[[Restore Project|Restore]] the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and involves backing up and restoring the SQL project database(s). It should be performed while there are no users using Promis.e/Bentley Substation. &lt;strong&gt;SQL Server Management Studio&lt;/strong&gt; is included with some Promis.e and Bentley Substation packages, otherwise see [[Install SQL Server Management Studio]]. SQL Server Management Studio can be installed on a machine other than the source and destination servers, but you will need access to the servers&amp;#39; hard drives in order to retrieve and copy the database backup file.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;[[Backup Project|Backup the critical projects using Project Manager]] while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;Backup the SQL project database(s) on the source server using SQL Server Management Studio&lt;/a&gt;.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; Determine the database to backup and the server that hosts it by looking at the [[Setup]]&lt;strong&gt; &amp;gt; Project Database&lt;/strong&gt; dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders now, just in case.&amp;nbsp; This way the backup of the project folders will be synchronized with the backup of the database.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx" rel="noopener noreferrer" target="_blank"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used to connect to the destination SQL Server and associate the login(s) with the database.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users, see the [[5824|Creating an SQL Server Login]] article. The script in the article should be executed for each project database being moved.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the &lt;strong&gt;Project Database&lt;/strong&gt; area of the [[Setup]] dialog of each workstation, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Ensure the projects affected by the move are accessible to users.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database/server.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database (.MDF) and transaction log files (.LDF) can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx" rel="noopener noreferrer" target="_blank"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server. SQL Server Management Studio is still required for this task. Note: A database named &amp;quot;promise&amp;quot; would have two related files: promise.mdf and promise_log.ldf. Both are required. These files are typically found in the &lt;a href="/products/electrical___instrumentation/w/electrical_and_instrumentation__wiki/6619/finding-the-sql-data-folder" rel="noopener noreferrer" target="_blank"&gt;SQL Server DATA folder&lt;/a&gt;.&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Backup Project]]&lt;/p&gt;
&lt;p&gt;[[Restore Project]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Finding the SQL Data folder]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/p&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Backup and Restore Project, Database Platform Support, promis.e, administration, SQL Server, how to, Bentley Substation, en, Project Management&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/24</link><pubDate>Wed, 06 Sep 2017 20:39:34 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 24 posted to OpenUtilities Wiki by Matt_P on 9/6/2017 8:39:34 PM&lt;br /&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.140&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Project Management&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Backup and Restore Project&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving Promis.e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance. Promis.e and Bentley Substation require a consistent 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), [[Backup Project|backup]] all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;[[Restore Project|Restore]] the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software. &lt;strong&gt;SQL Server Management Studio&lt;/strong&gt; is included with some Promis.e and Bentley Substation packages, otherwise see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;[[Backup Project|Backup the critical projects using Project Manager]] while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt;.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The database to backup and the server that hosts it can be determined by looking at the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders now, just in case.&amp;nbsp; This way the backup of the project folders will be synchronized with the backup of the database.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx" rel="noopener noreferrer" target="_blank"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used to connect to the SQL Server and associate the login(s) with the database.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] article.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the &lt;strong&gt;Project Database&lt;/strong&gt; area of the [[Setup]] dialog of each workstation, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Ensure the projects affected by the move are accessible to users.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database/server.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database (.MDF) and transaction log files (.LDF) can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx" rel="noopener noreferrer" target="_blank"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server. A database named &amp;quot;promise&amp;quot; would have two related files: promise.mdf and promise_log.ldf. Both are required. These files are typically found in the SQL Server &lt;a href="/products/electrical___instrumentation/w/electrical_and_instrumentation__wiki/6619/finding-the-sql-data-folder" rel="noopener noreferrer" target="_blank"&gt;DATA folder&lt;/a&gt;. &lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Backup Project]]&lt;/p&gt;
&lt;p&gt;[[Restore Project]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[Finding the SQL Data folder]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx" rel="noopener noreferrer" target="_blank"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" alt=" " height="60" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" width="189" /&gt;&lt;/p&gt;
&lt;table style="background-color:#dce5f0;border:0px solid #dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Backup and Restore Project, Database Platform Support, promis.e, administration, SQL Server, how to, Bentley Substation, en, Project Management&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/23</link><pubDate>Thu, 18 May 2017 04:10:08 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 23 posted to OpenUtilities Wiki by Matt_P on 5/18/2017 4:10:08 AM&lt;br /&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.13.96&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Project Management&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Backup and Restore Project&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving Promis.e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance. Promis.e and Bentley Substation require a consistent 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), [[Backup Project|backup]] all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;[[Restore Project|Restore]] the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software. &lt;strong&gt;SQL Server Management Studio&lt;/strong&gt; is included with some promis.e and Bentley Substation packages, otherwise see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express).&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The database to backup and the server that hosts it can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used to connect to the SQL Server and associate the login(s) with the database.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] article.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the &lt;strong&gt;Project Database&lt;/strong&gt; area of the [[Setup]] dialog of each workstation, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Ensure the projects affected by the move are accessible to users.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database/server.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Backup Project]]&lt;/p&gt;
&lt;p&gt;[[Restore Project]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " width="189" height="60" /&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Backup and Restore Project, Database Platform Support, promis.e, administration, SQL Server, how to, Bentley Substation, en, Project Management, SELECTsupport&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/22</link><pubDate>Tue, 01 Sep 2015 20:48:18 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 22 posted to OpenUtilities Wiki by Matt_P on 9/1/2015 8:48:18 PM&lt;br /&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.137&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e Functionality&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Design Features&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), [[Backup Project|backup]] all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;[[Restore Project|Restore]] the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software. &lt;strong&gt;SQL Server Management Studio&lt;/strong&gt; is included with some promis.e and Bentley Substation packages, otherwise see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express).&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The database to backup and the server that hosts it can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used to connect to the SQL Server and associate the login(s) with the database.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] article.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the &lt;strong&gt;Project Database&lt;/strong&gt; area of the [[Setup]] dialog of each workstation, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Ensure the projects affected by the move are accessible to users.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database/server.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Backup Project]]&lt;/p&gt;
&lt;p&gt;[[Restore Project]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/p&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Matt_P&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, promis.e Functionality, SQL Server, how to, Bentley Substation, en, Design Features, Project Management, SELECTsupport, Platform Support&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/21</link><pubDate>Mon, 22 Jun 2015 19:59:21 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 21 posted to OpenUtilities Wiki by Matt_P on 6/22/2015 7:59:21 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.137&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e Functionality&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Design Features&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), [[Backup Project|backup]] all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;[[Restore Project|Restore]] the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software. &lt;strong&gt;SQL Server Management Studio&lt;/strong&gt; is included with some promis.e and Bentley Substation packages, otherwise see [[Install SQL Server Management Studio]].&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express).&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The database to backup and the server that hosts it can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used to connect to the SQL Server and associate the login(s) with the database.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] article.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the &lt;strong&gt;Project Database&lt;/strong&gt; area of the [[Setup]] dialog of each workstation, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Ensure the projects affected by the move are accessible to users.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database/server.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Backup Project]]&lt;/p&gt;
&lt;p&gt;[[Restore Project]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, promis.e Functionality, SQL Server, how to, Bentley Substation, en, Design Features, Project Management, SELECTsupport, Platform Support&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/20</link><pubDate>Wed, 18 Mar 2015 16:11:15 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 20 posted to OpenUtilities Wiki by Matt_P on 3/18/2015 4:11:15 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e Functionality&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Design Features&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), [[Backup Project|backup]] all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;[[Restore Project|Restore]] the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Project Database area of the [[Setup]] dialog of each workstation, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Ensure the projects affected by the move are accessible to users.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Backup Project]]&lt;/p&gt;
&lt;p&gt;[[Restore Project]]&lt;/p&gt;
&lt;p&gt;[[Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[Creating an SQL Server Login]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, promis.e Functionality, SQL Server, how to, Bentley Substation, Design Features, Project Management, SELECTsupport, Platform Support&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/19</link><pubDate>Wed, 13 Aug 2014 20:43:16 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 19 posted to OpenUtilities Wiki by Matt_P on 8/13/2014 8:43:16 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e, Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e Functionality&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Design Features&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), backup all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Project Database area of the [[Setup]] dialog of each workstation, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;Ensure the projects affected by the move are accessible to users.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target="_blank" href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, promis.e Functionality, SQL Server, how to, Bentley Substation, Design Features, Project Management, SELECTsupport, Platform Support&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/18</link><pubDate>Tue, 11 Feb 2014 15:30:02 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 18 posted to OpenUtilities Wiki by Matt_P on 2/11/2014 3:30:02 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" src="/cfs-file.ashx/__key/communityserver-components-sitefiles/TSG-Logo.png" alt=" " width="189" height="60" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e Functionality&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Design Features&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), backup all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the destination machine &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Project Database area of the [[Setup]] dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Database Platform Support, promis.e, administration, promis.e Functionality, SQL Server, how to, Bentley Substation, Design Features, Project Management, SELECTsupport, Platform Support&lt;/div&gt;
</description></item><item><title>Moving Projects</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/17</link><pubDate>Wed, 22 Jan 2014 16:57:45 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 17 posted to OpenUtilities Wiki by Matt_P on 1/22/2014 4:57:45 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt=" " src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="189" height="60" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;through 08.11.12.xx&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e Functionality&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Design Features&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), backup all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See [[3594|Creating and Updating the Project Database]]. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;On the destination machine &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Project Database area of the [[Setup]] dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, administration, promis.e Functionality, SQL Server, how to, Bentley Substation, Design Features, Project Management, SELECTsupport&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/16</link><pubDate>Tue, 01 Oct 2013 20:16:12 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 16 posted to OpenUtilities Wiki by Matt_P on 10/1/2013 8:16:12 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis.e Functionality&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Design Features&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), backup all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote. When moving to a different workstation in a single-user environment, the &amp;quot;destination machine&amp;quot; would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;On the destination machine &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Project Database area of the [[Setup]] dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, promis.e Functionality, SQL Server, how to, Bentley Substation, Design Features, SELECTsupport&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/15</link><pubDate>Mon, 12 Aug 2013 14:37:28 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 15 posted to OpenUtilities Wiki by Matt_P on 8/12/2013 2:37:28 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;On the source machine(s), backup all the projects to be moved using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving or changing anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote. When moving to a different workstation in a single-user environment the destination machine would be the new workstation and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine, and this step may have already been completed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database to which the software is currently connected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;On the destination machine &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Project Database area of the [[Setup]] dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="LEARN Server" href="http://lms.bentley.com"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, SELECTsupport, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/14</link><pubDate>Mon, 12 Aug 2013 14:24:59 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 14 posted to OpenUtilities Wiki by Matt_P on 8/12/2013 2:24:59 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup all the projects on the source machine(s) using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if applicable and not already existing) and create a new project database on it.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&amp;nbsp; When moving to a different workstation in a single-user environment, this is done on the Setup dialog on the new machine.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Project Database area of the Setup dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="LEARN Server" href="http://lms.bentley.com"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, SELECTsupport, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/13</link><pubDate>Thu, 25 Jul 2013 21:09:14 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 13 posted to OpenUtilities Wiki by Matt_P on 7/25/2013 9:09:14 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e or Bentley Substation to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e and Bentley Substation require a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup all the projects using&lt;em&gt; Project Manager&lt;/em&gt; while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing) and create a new project database on it.&amp;nbsp; See the [[3594|Creating and Updating the Project Database]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Specify the new server name and database name in the Project Database area of the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the paths you specify and inserts the project data into the database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Install SQL Server on the destination machine (if not already existing)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Move the project folders to the new location, if applicable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;On the Project Database area of the Setup dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Decommission the old database.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[3594|Creating and Updating the Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="LEARN Server" href="http://lms.bentley.com"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, SELECTsupport, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/12</link><pubDate>Thu, 25 Jul 2013 20:57:20 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 12 posted to OpenUtilities Wiki by Matt_P on 7/25/2013 8:57:20 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e requires a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup all the projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and create a new project database on it.&amp;nbsp; See the [[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]] TechNote.&lt;/li&gt;
&lt;li&gt;Connect promis&amp;bull;e to the new database on the Project Database area of the [[Setup]] dialog.&lt;/li&gt;
&lt;li&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the destination you specify and inserts the project data into the database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server, and should be performed while there are no users using the software.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the [[Setup]] dialog.&lt;/li&gt;
&lt;li&gt;Backup the project folders, just in case.&amp;nbsp; This way you will have a backup of the database and the project folders while they are synchronized.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/li&gt;
&lt;li&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/li&gt;
&lt;li&gt;Move the project folders to the new location, if applicable.&lt;/li&gt;
&lt;li&gt;On the Project Database area of the Setup dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/li&gt;
&lt;li&gt;Decommission the old database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="LEARN Server" href="http://lms.bentley.com"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, SELECTsupport, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/11</link><pubDate>Thu, 11 Jul 2013 16:14:55 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 11 posted to OpenUtilities Wiki by Matt_P on 7/11/2013 4:14:55 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="60" width="189" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" align="left" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;, Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;h1&gt;Background&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e requires a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Steps to Accomplish&lt;/h1&gt;
&lt;h2&gt;Method 1&lt;/h2&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup all the projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and create a new project database on it.&amp;nbsp; See the [[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]] TechNote.&lt;/li&gt;
&lt;li&gt;Connect promis&amp;bull;e to the new database on the Project Database area of the &lt;i&gt;promis-e [[Setup]]&lt;/i&gt; dialog.&lt;/li&gt;
&lt;li&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the destination you specify and inserts the project data into the database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h2&gt;Method 2&lt;/h2&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the &lt;i&gt;promis-e [[Setup]] &lt;/i&gt;dialog.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/li&gt;
&lt;li&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/li&gt;
&lt;li&gt;Move the project folders to the new location, if applicable.&lt;/li&gt;
&lt;li&gt;On the Project Database area of the&lt;i&gt; promis-e Setup&lt;/i&gt; dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/li&gt;
&lt;li&gt;Decommission the old database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="LEARN Server" href="http://lms.bentley.com"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Comments or Corrections?&lt;/h1&gt;
&lt;p&gt;Bentley&amp;#39;s Technical Support Group requests that you please submit any comments you have on this Wiki article to the &amp;quot;Comments&amp;quot; area below. THANK YOU!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/10</link><pubDate>Tue, 11 Jun 2013 20:23:30 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Elisabeth Pry</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 10 posted to OpenUtilities Wiki by Elisabeth Pry on 6/11/2013 8:23:30 PM&lt;br /&gt;
&lt;h1&gt;&lt;b&gt;&lt;img width="189" height="60" style="border-width:0px;" alt="" src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" /&gt;&lt;/b&gt;&lt;/h1&gt;
&lt;table align="left" style="border:0px solid #dce5f0;width:500px;background-color:#dce5f0;" border="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;span style="font-size:medium;"&gt;&lt;b&gt;Applies To&amp;nbsp;&lt;/b&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;promis&amp;bull;e &amp;amp; Bentley Substation&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;All&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Environment:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Subarea:&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;Original Author:&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Bentley Technical Support Group&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e requires a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Method 1&lt;/h1&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup all the projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and create a new project database on it.&amp;nbsp; See the [[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]] TechNote.&lt;/li&gt;
&lt;li&gt;Connect promis&amp;bull;e to the new database on the Project Database area of the &lt;i&gt;promis-e [[Setup]]&lt;/i&gt; dialog.&lt;/li&gt;
&lt;li&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the destination you specify and inserts the project data into the database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h1&gt;Method 2&lt;/h1&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the &lt;i&gt;promis-e [[Setup]] &lt;/i&gt;dialog.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/li&gt;
&lt;li&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/li&gt;
&lt;li&gt;Move the project folders to the new location, if applicable.&lt;/li&gt;
&lt;li&gt;On the Project Database area of the&lt;i&gt; promis-e Setup&lt;/i&gt; dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/li&gt;
&lt;li&gt;Decommission the old database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="KnowledgeBase" href="http://appsnet.bentley.com/kbase/"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="LEARN Server" href="http://lms.bentley.com"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Comments or Corrections?&lt;/h1&gt;
&lt;p&gt;Bentley&amp;#39;s Technical Support Group requests that you please submit any comments you have on this Wiki article to the &amp;quot;Comments&amp;quot; area below. THANK YOU!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div class="hr"&gt;&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/9</link><pubDate>Wed, 04 Apr 2012 20:10:44 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 9 posted to OpenUtilities Wiki by Matt_P on 4/4/2012 8:10:44 PM&lt;br /&gt;
&lt;p&gt;&lt;a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"&gt;&lt;/a&gt; &lt;a href="http://selectservices.bentley.com/en-US"&gt;&lt;img src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" border="0" height="56" width="175" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Document Information&lt;/h1&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;b&gt;Document Type:&lt;/b&gt; TechNote&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Product(s):&lt;/b&gt; promis&amp;bull;e, Bentley Substation&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Version(s):&lt;/b&gt; All&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Original Author:&lt;/b&gt; &lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h1&gt;Overview&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e requires a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Method 1&lt;/h1&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup all the projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and create a new project database on it.&amp;nbsp; See the [[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]] TechNote.&lt;/li&gt;
&lt;li&gt;Connect promis&amp;bull;e to the new database on the Project Database area of the &lt;i&gt;promis-e [[Setup]]&lt;/i&gt; dialog.&lt;/li&gt;
&lt;li&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the destination you specify and inserts the project data into the database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h1&gt;Method 2&lt;/h1&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the &lt;i&gt;promis-e [[Setup]] &lt;/i&gt;dialog.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;Restore the backup&lt;/a&gt; (.BAK) created in step 2, again using SQL Server Management Studio.&lt;/li&gt;
&lt;li&gt;Create the login(s) that will be used by promis&amp;bull;e to connect to the SQL Server.&amp;nbsp; This step is necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users.&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/li&gt;
&lt;li&gt;Move the project folders to the new location, if applicable.&lt;/li&gt;
&lt;li&gt;On the Project Database area of the&lt;i&gt; promis-e Setup&lt;/i&gt; dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/li&gt;
&lt;li&gt;Decommission the old database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 4, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://lms.bentley.com" title="LEARN Server"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Comments or Corrections?&lt;/h1&gt;
&lt;p&gt;Bentley&amp;#39;s Technical Support Group requests that you please submit any comments you have on this Wiki article to the &amp;quot;Comments&amp;quot; area below. THANK YOU!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div class="hr"&gt;&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/8</link><pubDate>Thu, 23 Feb 2012 17:18:12 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 8 posted to OpenUtilities Wiki by Matt_P on 2/23/2012 5:18:12 PM&lt;br /&gt;
&lt;p&gt;&lt;a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"&gt;&lt;/a&gt; &lt;a href="http://selectservices.bentley.com/en-US"&gt;&lt;img src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="56" border="0" width="175" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Document Information&lt;/h1&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;b&gt;Document Type:&lt;/b&gt; TechNote&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Product(s):&lt;/b&gt; promis&amp;bull;e, Bentley Substation&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Version(s):&lt;/b&gt; All&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Original Author:&lt;/b&gt; &lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h1&gt;Overview&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving projects from a network configuration to a local configuration so work can be done away from the network.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e requires a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Method 1&lt;/h1&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup all the projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and create a new project database on it.&amp;nbsp; See the [[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]] TechNote.&lt;/li&gt;
&lt;li&gt;Connect promis&amp;bull;e to the new database on the Project Database area of the &lt;i&gt;promis-e [[Setup]]&lt;/i&gt; dialog.&lt;/li&gt;
&lt;li&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the destination you specify and inserts the project data into the database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Backing up projects does not delete them.&amp;nbsp; Therefore it is possible to end up with instances of the same project on multiple machines and users unknowingly working on different instances.&amp;nbsp; It is up to the user to implement or enforce some method of control to avoid this situation.&lt;/p&gt;
&lt;h1&gt;Method 2&lt;/h1&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the &lt;i&gt;promis-e [[Setup]] &lt;/i&gt;dialog.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;restore the backup&lt;/a&gt; (.BAK) created in step 2 again using SSMSE.&lt;/li&gt;
&lt;li&gt;Create an SQL Server login and associate the ecaduser User of the project database to the server SQL login.&amp;nbsp; This step is often necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users (such as the &amp;quot;ecaduser&amp;quot; login the promis&amp;bull;e project database script creates).&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/li&gt;
&lt;li&gt;Move the project folders to the new location, if applicable.&lt;/li&gt;
&lt;li&gt;On the Project Database area of the&lt;i&gt; promis-e Setup&lt;/i&gt; dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/li&gt;
&lt;li&gt;Decommission the old database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 3, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://lms.bentley.com" title="LEARN Server"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Comments or Corrections?&lt;/h1&gt;
&lt;p&gt;Bentley&amp;#39;s Technical Support Group requests that you please submit any comments you have on this Wiki article to the &amp;quot;Comments&amp;quot; area below. THANK YOU!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div class="hr"&gt;&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/7</link><pubDate>Fri, 09 Sep 2011 20:31:48 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 7 posted to OpenUtilities Wiki by Matt_P on 9/9/2011 8:31:48 PM&lt;br /&gt;
&lt;p&gt;&lt;a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"&gt;&lt;/a&gt; &lt;a href="http://selectservices.bentley.com/en-US"&gt;&lt;img src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" height="56" border="0" width="175" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Document Information&lt;/h1&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;b&gt;Document Type:&lt;/b&gt; TechNote&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Product(s):&lt;/b&gt; promis&amp;bull;e, Bentley Substation&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Version(s):&lt;/b&gt; All&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Original Author:&lt;/b&gt; &lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h1&gt;Overview&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e requires a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Method 1&lt;/h1&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup all the projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and create a new project database on it.&amp;nbsp; See the [[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]] TechNote.&lt;/li&gt;
&lt;li&gt;Connect promis&amp;bull;e to the new database on the Project Database area of the &lt;i&gt;promis-e [[Setup]]&lt;/i&gt; dialog.&lt;/li&gt;
&lt;li&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the destination you specify and inserts the project data into the database.&lt;/li&gt;
&lt;/ol&gt;
&lt;h1&gt;Method 2&lt;/h1&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the &lt;i&gt;promis-e [[Setup]] &lt;/i&gt;dialog.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;restore the backup&lt;/a&gt; (.BAK) created in step 2 again using SSMSE.&lt;/li&gt;
&lt;li&gt;Create an SQL Server login and associate the ecaduser User of the project database to the server SQL login.&amp;nbsp; This step is often necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users (such as the &amp;quot;ecaduser&amp;quot; login the promis&amp;bull;e project database script creates).&amp;nbsp; See the [[5824|Creating an SQL Server Login]] TechNote.&lt;/li&gt;
&lt;li&gt;Move the project folders to the new location, if applicable.&lt;/li&gt;
&lt;li&gt;On the Project Database area of the&lt;i&gt; promis-e Setup&lt;/i&gt; dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/li&gt;
&lt;li&gt;Decommission the old database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 3, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]]&lt;/p&gt;
&lt;p&gt;[[5824|Creating an SQL Server Login]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://lms.bentley.com" title="LEARN Server"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Comments or Corrections?&lt;/h1&gt;
&lt;p&gt;Bentley&amp;#39;s Technical Support Group requests that you please submit any comments you have on this Wiki article to the &amp;quot;Comments&amp;quot; area below. THANK YOU!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div class="hr"&gt;&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation&lt;/div&gt;
</description></item><item><title>Moving Projects [TN]</title><link>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects/revision/6</link><pubDate>Fri, 24 Jun 2011 18:47:30 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4660aad2-024d-40fa-b2a0-94b9d2bee7c2</guid><dc:creator>Matt_P</dc:creator><comments>https://communities.bentley.com/products/utility_network_analysis___design/w/utility_network_analysis_and_design_wiki/5124/moving-projects#comments</comments><description>Revision 6 posted to OpenUtilities Wiki by Matt_P on 6/24/2011 6:47:30 PM&lt;br /&gt;
&lt;p&gt;&lt;a href="http://selectservices.bentley.com/en-US" title="SELECT Services Online"&gt;&lt;/a&gt;  &lt;a href="http://selectservices.bentley.com/en-US"&gt;&lt;img src="/Other/Old_Site_Files/Bentley_Folders/m/support/17560/download.aspx" width="175" border="0" height="56" alt="" /&gt;&lt;/a&gt; &lt;/p&gt;
&lt;h1&gt;Document Information&lt;/h1&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;b&gt;Document Type:&lt;/b&gt; TechNote&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Product(s):&lt;/b&gt; promis&amp;bull;e&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Version(s):&lt;/b&gt; All&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Original Author:&lt;/b&gt; &lt;a href="/members/matt_5f00_p/default.aspx"&gt;Matt_P&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h1&gt;Overview&lt;/h1&gt;
&lt;p&gt;It is sometimes necessary or desired to move projects or the project database from one computer to another.&lt;br /&gt;&lt;br /&gt;Common situations include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moving promis&amp;bull;e to a new workstation in a single user environment.&lt;/li&gt;
&lt;li&gt;Moving the projects from a &amp;ldquo;standalone&amp;rdquo; workstation to a network server(s) to enable the sharing of projects in a multi-user environment. Check with the IT department to ensure that the proper machine has been chosen to host the SQL Server.&lt;/li&gt;
&lt;li&gt;Moving the database from one server to another.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Please note that after moving from a local setup to a network setup you may notice a decrease in performance.&amp;nbsp; promis&amp;bull;e requires a maintained 35 megabits per second transfer rate, and what is actually achieved by the network is not the same as the equipment ratings of the network.&lt;/p&gt;
&lt;h1&gt;Method 1&lt;/h1&gt;
&lt;p&gt;The most reliable way to &amp;quot;move&amp;quot; the SQL project data, and the method Bentley Technical Support analysts are most able to support, is the following process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup all the projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and create a new project database on it.&amp;nbsp; See the [[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]] TechNote.&lt;/li&gt;
&lt;li&gt;Connect promis&amp;bull;e to the new database on the Project Database area of the &lt;i&gt;promis-e Setup&lt;/i&gt; dialog.&lt;/li&gt;
&lt;li&gt;Restore the project backup files (.PRJ files) created in step 1. This will extract the project folders to the destination you specify and inserts the project data into the database.&lt;/li&gt;
&lt;/ol&gt;
&lt;h1&gt;Method 2&lt;/h1&gt;
&lt;p&gt;This method requires some familiarity with the administration of SQL Server.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Backup the critical projects using Project Manager while the existing configuration is still valid (before moving anything).&amp;nbsp; Projects are backed up individually, and each project backup results in a .PRJ archive file.&amp;nbsp; These backups could be restored into a new database if moving the database is not successful.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;Backup the SQL project database using SQL Server Management Studio&lt;/a&gt; (including Express), which is available from Microsoft and also included as an optional install with the promis&amp;bull;e installation file.&amp;nbsp; This will result in a .BAK file.&amp;nbsp; The server name and database name for the project database can be determined on the &lt;i&gt;promis-e Setup dialog&lt;/i&gt;.&lt;/li&gt;
&lt;li&gt;Install SQL Server on the destination machine (if not already existing) and &lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;restore the backup&lt;/a&gt; (.BAK) created in step 2 again using SSMSE.&lt;/li&gt;
&lt;li&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;Create a SQL login&lt;/a&gt; and associate the ecaduser User of the project database to the server SQL login.&amp;nbsp; This step is often necessary because the login is associated with the server, not the database, so transferring the database does not transfer the login.&amp;nbsp; If using Windows Authentication, each connecting user would need to be setup; if using SQL Server Authentication, a generic login can be created and used by all users (such as the &amp;quot;ecaduser&amp;quot; login the promis&amp;bull;e project database script creates).&amp;nbsp; See script example below.&lt;/li&gt;
&lt;li&gt;Move the project folders to the new location, if applicable.&lt;/li&gt;
&lt;li&gt;On the Project Database area of the&lt;i&gt; promis-e Setup&lt;/i&gt; dialog, set the configuration to use new SQL server and/or database, and the appropriate login information.&lt;/li&gt;
&lt;li&gt;Decommission the old database.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Alternatively, instead of backing up and restoring the SQL database in steps 2 and 3, the database and transaction log files can be moved to the new server machine and &amp;quot;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;attached&lt;/a&gt;&amp;quot; to the new SQL Server.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;The following script adds the &amp;quot;ecaduser&amp;quot; login with a &amp;quot;Ecad1pass&amp;quot; password for SQL Server Authentication access to the SQL Server and adds the &amp;quot;ecaduser&amp;quot; user to the promiseX database and links it to the login.&amp;nbsp; It can be run using SSMSE after restoring the project database.&amp;nbsp; Substitute the correct database name for &amp;ldquo;promiseX&amp;rdquo; before executing the script.&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;br /&gt;&lt;span style="font-family:courier new,courier;"&gt;if not exists (select * from syslogins WHERE loginname=N&amp;#39;ecaduser&amp;#39;)&lt;br /&gt;begin&lt;br /&gt;&amp;nbsp;&amp;nbsp; EXEC sp_addlogin &amp;#39;ecaduser&amp;#39;,&amp;#39;Ecad1pass&amp;#39;,&amp;#39;promiseX&amp;#39;;&lt;br /&gt;&amp;nbsp;&amp;nbsp; ALTER LOGIN [ecaduser] WITH DEFAULT_DATABASE=[promiseX], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF;&lt;br /&gt;end&lt;br /&gt;GO&lt;br /&gt;use promiseX&lt;br /&gt;GO&lt;br /&gt;if not exists(select * from sysusers WHERE name=N&amp;#39;ecaduser&amp;#39;)&lt;br /&gt;&amp;nbsp;&amp;nbsp; EXEC sp_adduser &amp;#39;ecaduser&amp;#39;,&amp;#39;ecaduser&amp;#39;,&amp;#39;db_owner&amp;#39;&lt;br /&gt;GO&lt;br /&gt;ALTER USER ecaduser WITH LOGIN = ecaduser;&lt;br /&gt;GO&lt;br /&gt;ALTER USER ecaduser WITH DEFAULT_SCHEMA = dbo;&lt;br /&gt;GO&lt;/span&gt;&lt;/p&gt;
&lt;p style="padding-left:30px;"&gt;&lt;span style="font-family:courier new,courier;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h1&gt;See Also&lt;/h1&gt;
&lt;p&gt;[[Creating and Updating the promis.e Project Database|Creating and Updating the promis&amp;bull;e Project Database]]&lt;/p&gt;
&lt;p&gt;[[SELECTsupport TechNotes and FAQs]]&lt;/p&gt;
&lt;h1&gt;External Links&lt;/h1&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms187510.aspx"&gt;How to: Back Up a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms177429.aspx"&gt;How to: Restore a Database Backup (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/ms190209.aspx"&gt;How to: Attach a Database (SQL Server Management Studio)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;How to: Create a SQL Server Login&lt;/a&gt;&lt;a href="http://msdn.microsoft.com/en-us/library/aa337562.aspx"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://appsnet.bentley.com/kbase/" title="KnowledgeBase"&gt;Bentley Technical Support KnowledgeBase&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://lms.bentley.com" title="LEARN Server"&gt;Bentley LEARN Server&lt;/a&gt;&lt;/p&gt;
&lt;h1&gt;Comments or Corrections?&lt;/h1&gt;
&lt;p&gt;Bentley&amp;#39;s Technical Support Group requests that you please submit any comments you have on this Wiki article to the &amp;quot;Comments&amp;quot; area below. THANK YOU!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div class="hr"&gt;&lt;/div&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: promis.e, sql server, Bentley Substation&lt;/div&gt;
</description></item></channel></rss>