Estate Master Estate Master Enterprise Database Database Management Software Installation and Configuration Guide

Installation and Configuration Guide
2
Estate Master Enterprise Database
Table of Contents
Part I Introduction to Estate Master Enterprise
Database
4
1 Introduction ................................................................................................................................... 4
2 Typical Setup...................................................................................................................................
Scenarios
5
Single User - Single
..........................................................................................................................................................
Site
Multi User - Single
..........................................................................................................................................................
Site
Multi User - Multi
..........................................................................................................................................................
Site
5
6
7
3 System Requirements
................................................................................................................................... 8
10
Part II Installation and Configuration
1 The Database
...................................................................................................................................
Management Tool
10
2 Install SQL Server
................................................................................................................................... 11
3 Setup and Connect
...................................................................................................................................
to the Database
11
Database has..........................................................................................................................................................
not been setup previously
Database has..........................................................................................................................................................
been setup previously
12
15
4 Upgrading the
...................................................................................................................................
Database
18
5 Backup the Database
................................................................................................................................... 20
6 Restore the ...................................................................................................................................
Database
22
Part III Using the Enterprise Database with Estate
Master
25
1 Preparing Data
...................................................................................................................................
for Exporting
25
2 Exporting to...................................................................................................................................
the Database
28
3 Importing from
...................................................................................................................................
the Database
31
4 Exporting Reminders
................................................................................................................................... 33
35
Part IV Advanced Instructions
1 SQL Express
...................................................................................................................................
2008 Installation Guide
35
2 Permission Requirements
................................................................................................................................... 45
3 SQL Replication
................................................................................................................................... 47
49
Part V Licence Agreement
© 2011 Estate Master Pty Ltd
Part
I
4
Estate Master Enterprise Database
1
Introduction to Estate Master Enterprise Database
1.1
Introduction
This operations manual is a guide for using
the Estate Master Enterprise Database
developed in Microsoft SQL Server and
.NET. It is a central data management tool
that allows the user to archive development
cash flows created in the Estate Master DF
(Development Feasibility), DM (Development
Management) and Estate Master IA
(Investment Appraisal) software.
It is available to all users of Estate Master
DF and DM version 3.xx and above, and
Estate Master IA version 2.xx and above .
When using it in conjunction with Estate
Master CC (Corporate Consolidation), it
allows users to generate consolidate or
comparison reports for selected cash flows,
projects or portfolios to calculate forecasted
and actual investment returns including,
development profit, internal rate of return
and net present value.
The Estate Master Enterprise Database can
be used to:
· Archive all input and cash flow data
from Estate Master DF, DM and IA;
· Generate comparison summary and
cash flow reports for an unlimited
number of development options (when
used with EM CC).
· Generate consolidated summary and
cash flow reports for an unlimited
number of development stages (when
used with EM CC).
If you have any queries or suggestions for improvements, please contact us:
Estate Master Pty Ltd
GPO Box 2748
Sydney NSW 2001 Australia
Tel: 61 2 8198 7600
Fax: 61 2 9241 6854
Email: [email protected]
© 2011 Estate Master Pty Ltd
Introduction to Estate Master Enterprise Database
1.2
Typical Setup Scenarios
1.2.1
Single User - Single Site
5
This type of setup suits clients with the following characteristics:
· Small companies or individuals.
· A single user of the Estate Master DF/DM/IA/CC software.
· Needs to connect to the Estate Master Enterprise Database.
If a server is available on the local network and it can support SQL Server, then the Enterprise
Database can be installed on that server, with the Estate Master DF/DM/IA/CC user connecting to it
over the LAN.
Alternatively, if no server is available or it is preferred to setup SQL Server on a dedicated workstation,
then the Enterprise Database can be installed on the same workstation that has Estate Master DF/DM/
IA/CC installed.
© 2011 Estate Master Pty Ltd
6
1.2.2
Estate Master Enterprise Database
Multi User - Single Site
This type of setup suits clients with the following characteristics:
· Single office/site.
· Multiple users of the Estate Master DF/DM/IA/CC software at the one office/site.
· Needs to connect to the Estate Master Enterprise Database on a central server at the one office/
site.
It assumes that a server is available on the local network that can support SQL Server and the
Enterprise Database, with the Estate Master DF/DM/IA/CC user connecting to it over the LAN.
© 2011 Estate Master Pty Ltd
Introduction to Estate Master Enterprise Database
1.2.3
7
Multi User - Multi Site
This type of setup suits clients with the following characteristics:
· Medium to large companies.
· Multiple offices/sites.
· Multiple users of the Estate Master DF/DM/IA/CC software across the multiple offices/sites.
· Needs to connect to the Estate Master Enterprise Database on a central server at one of the
offices.
Multiple offices/sites include other offices or branches (national or international) or remote locations,
such as home offices, site offices or mobile users.
If there are multiple offices within an organisation that each house a server, an option may be to install
the Estate Master Enterprise Database at each location and then synchronise it with a main central
server using SQL Replication. This will allow users to connect to their own local Enterprise Database
over a LAN and then have it synchronise over a WAN to the main database when there is less
bandwidth activity (ie after hours).
© 2011 Estate Master Pty Ltd
8
1.3
Estate Master Enterprise Database
System Requirements
To install and operate Estate Master Enterprise Database efficiently, the following is recommended:
· PC with an Intel Core 2 Duo (3GHz) or Quad (2.4Ghz) minimum processor (or equivalent)
· Microsoft Windows 2000 or later operating system.
· Estate Master DF or DM 3.1 or higher or IA 2.1 or higher (for export that data from and importing the
data to).
· Microsoft Internet Explorer 5.1 or higher.
· Microsoft .Net Framework 3.5.
· Microsoft Report Viewer 2008.
· Microsoft SQL Server 2005/2008 Standard/Enterprise or SQL Server Express 2005/2008.
· 2GBMb RAM or higher.
· CD Drive (if installing from CD).
· Modem and internet connection (for downloading files and obtaining tech support).
SQL Server Standard or SQL Express Edition?
Before installing SQL Server on your network, please consider the differences between both the full
version and the express edition version.
Edition
Licensing
Max Database Size
RAM
Number of CPU's
Express
Free
10 GB
1 GB
1
SQL Server 2008
Standard/Enterprise
Licence Required
524 PB
64 GB
4
© 2011 Estate Master Pty Ltd
Part
II
10
Estate Master Enterprise Database
2
Installation and Configuration
2.1
The Database Management Tool
To setup the Estate Master Enterprise Database on your network, a Database Management Utility is
installed when you install any Estate Master software product. It will allow you to:
1. Install SQL Server on your system.
2. Setup the Estate Master Enterprise Database and Configure a connection to it.
3. Upgrade the Estate Master Enterprise Database when updates are released.
4. Backup the Estate Master Enterprise Database.
5. Restore the Estate Master Enterprise Database.
The Management Tool can be accessed via the Estate Master menu in Windows Start Programs.
© 2011 Estate Master Pty Ltd
Installation and Configuration
2.2
11
Install SQL Server
The Estate Master Enterprise Database requires Microsoft SQL Server to be installed somewhere on
your network for the Enterprise Database to be setup and configured.
1. Step 1 of the configuration tool displays the status of any SQL Servers on your network.
and it has detected SQL Servers on the network, then you will probably not be
2. If there is a
required to download and install another SQL Server and that you will be able to utilise one of
existing ones for the Enterprise Database.
and it has not detected any SQL Servers on the network, then you may need to
3. If there is a
download and install SQL Server by clicking on the 'Download' button. Please check with your
Network Administrator being installing SQL Server on your network.
4. If you need to download SQL Server Express from Microsoft, you will not require the 'Advanced
Services' version. The suitable version should be approx 30-50MB in size.
Please Note:
· For instructions on installing SQL Server Express Edition, please refer to the Advanced
Instructions section.
· For instructions on installing on Windows Vista Operating Systems, please refer to the
Advanced Instructions section.
2.3
Setup and Connect to the Database
Once Microsoft SQL Server has been installed or you choose to utilise an existing one, the next step is
to setup and connect to the Estate Master Enterprise Database on that SQL Server.
1. Step 2 of the configuration tool displays the status of any connection from your system to the Estate
Master Enterprise Database connection on your network.
and it has connected to the Estate Master Enterprise Database, then you can
2. If there is a
proceed to Step 3.
and it could not connect to the Estate Master Enterprise Database, then you will
3. If there is a
need to click on 'Configure' to setup and connect to it.
Important Information
If the Enterprise Database has not been configured previously by any user on your network, and you
are the first Estate Master user to do so, go to Database HAS NOT BEEN setup previously.
If the Enterprise Database has been configured previously, and you just need to connect to it, go to
Database HAS BEEN setup previously.
© 2011 Estate Master Pty Ltd
12
2.3.1
Estate Master Enterprise Database
Database has not been setup previously
Important Information
Only 1 Estate Master Enterprise Database should be configured on your Network.
DO NOT configure a new Estate Master Enterprise Database before first consulting with your Network
Administrator to avoid installing and configuring multiple databases.
1. Select ‘New Database’
2. If SQL Server is installed then select the SQL Server name from the 'Server' list. If SQL Server
is not installed (ie SQL Server Express Edition is installed instead) then type server name
\SQLEXPRESS in the 'Server' box. If SQL Server Express is installed on the local machine you
are on, then the "server name" should be replaced with a "." (eg .\SQLEXPRESS)
3. If you are connected to a Windows domain then select ‘User Windows NT Integrated Security’.
This will be fine for anyone on the same domain as the server. If the server is on a workgroup
then the clients will have to specify a username and password. For this the client will require
SQL Management Studio Express to be installed. They can go properties of the server and
choose “SQL Server and Windows Authentication mode” then specify the sa password.
© 2011 Estate Master Pty Ltd
Installation and Configuration
13
4. If SQL Server is not installed then you may get an error when trying to select the SQL Server
name from server list. Click OK and then type the SQL Server name in the list.
5. Click ‘Test’ to test connection to the database. If it can establish a connection, a message will
appear – “Connection Successful”.
6. Click ‘Create’ to create the database. The following screens will appear. Once the process is
completed, click ‘Close’ to close the screen.The database should now be up to date.
Access Denied Error
If an 'Access Denied' error message appears when trying to create, backup or restore the Estate
Master Enterprise Database, the user may not have the proper permissions within SQL to ‘create a
database’.
To adjust these permissions, please refer to the Advanced Instructions
© 2011 Estate Master Pty Ltd
14
Estate Master Enterprise Database
7. The Estate Master Enterprise Database should now be up to date and setup on your network.
The database configuration file (EMDB.ini) will be saved in the Windows System folder (usually
C:\Windows\System32) of the system where it was configured and is ready to be distributed to
those who will be using the Estate Master Enterprise Database (refer to notes below).
The Database Configuration File (EMDB.ini)
The Database Configuration File (EMDB.ini) that gets created in the <Common Files
Folder>\System\Datastore directory (e.g C:\Program Files\Common Files\System\Datastore) after
setting up the Estate Master Enterprise Database on a server contains important information (i.e. the
SQL connection string) that allows users of the Estate Master DF, DM, IA and CC software to connect
to the database when exporting, importing and reporting cash flow data.
When the Estate Master Enterprise Database is set up and the configuration file is created, it is
advised that the IT Administrator copy the EMDB.ini file from this directory and place it in the same
directory of the other workstations/servers that will be running the Estate Master DF, DM or CC
software.
For 32-bit machines: C:\Program Files\Common Files\System\Datastore
For 64-bit machines: C:\Program Files (x86)\Common Files\System\Datastore
This will then allow these other workstations/servers to connect to the Estate Master Enterprise
Database without having any further configuration, depending on your network environment (e.g.
security permissions).
If the <Common Files Folder>\System\Datastore folder is not found when running the Database
Management Tool, then the following message will appear:
Backward Compatibility
In previous versions of the software, the EMDB.ini was stored in the Windows System folder (e.g
C:Windows\System32). To ensure backward compatibility, the EMDB.ini is now copied to this folder
when it is created. If the user doesnt have permissions to the Windows System folder, the following
message will appear:
This backward compatibility requirement applies to the following version of Estate Master and older:
·
·
·
·
DF – 4.11
DM – 4.11
CC – 6.4
IA – 3.12
© 2011 Estate Master Pty Ltd
Installation and Configuration
2.3.2
Database has been setup previously
1. Select ‘Use Existing Database’ and click ‘Build’ to show screen to configure connection to
database.
2. In the Data Link Properties 'Connection' tab:
· Select the Server Name from the list. Click ‘Refresh’ to update the list if necessary.
· Enter security information to log on to the server (ie username and password).
· Select Database Name from the list - the Estate Master Enterprise Database is called
EstateMasterData.
© 2011 Estate Master Pty Ltd
15
16
Estate Master Enterprise Database
3. Click ‘Test Connection’. If it can establish a connection, a message will appear – “Connection
Successful”.
4. The Estate Master Enterprise Database should now be up to date and setup on your network.
The database configuration file (EMDB.ini) will be saved in the Windows System32 folder of the
system where it was configured and is ready to be distributed to those who will be using the
Estate Master Enterprise Database (refer to notes below).
© 2011 Estate Master Pty Ltd
Installation and Configuration
17
The Database Configuration File (EMDB.ini)
The Database Configuration File (EMDB.ini) that gets created in the <Common Files
Folder>\System\Datastore directory (e.g C:\Program Files\Common Files\System\Datastore) after
setting up the Estate Master Enterprise Database on a server contains important information (i.e. the
SQL connection string) that allows users of the Estate Master DF, DM, IA and CC software to connect
to the database when exporting, importing and reporting cash flow data.
When the Estate Master Enterprise Database is set up and the configuration file is created, it is
advised that the IT Administrator copy the EMDB.ini file from this directory and place it in the same
directory of the other workstations/servers that will be running the Estate Master DF, DM or CC
software.
For 32-bit machines: C:\Program Files\Common Files\System\Datastore
For 64-bit machines: C:\Program Files (x86)\Common Files\System\Datastore
This will then allow these other workstations/servers to connect to the Estate Master Enterprise
Database without having any further configuration, depending on your network environment (e.g.
security permissions).
If the <Common Files Folder>\System\Datastore folder is not found when running the Database
Management Tool, then the following message will appear:
Backward Compatibility
In previous versions of the software, the EMDB.ini was stored in the Windows System folder (e.g
C:Windows\System32). To ensure backward compatibility, the EMDB.ini is now copied to this folder
when it is created. If the user doesnt have permissions to the Windows System folder, the following
message will appear:
This backward compatibility requirement applies to the following version of Estate Master and older:
·
·
·
·
DF – 4.11
DM – 4.11
CC – 6.4
IA – 3.12
© 2011 Estate Master Pty Ltd
18
2.4
Estate Master Enterprise Database
Upgrading the Database
Any time a new version of Estate Master installed, it is advised to check to see if any updates to
the Enterprise Database have also been installed and need to be applied.
1. If the database needs upgrading then click ‘Upgrade’. You will be informed that the database will
need to be backed up before you can proceed to conduct an upgrade.
2. Click 'OK' and a Save dialog will appear. Select a location and enter in a filename and click
'Save'
3. You can only backup to the same server as where the database is located. If you try to backup
to another machine, you will get the following error message and you will need to attempt to
backup again.
© 2011 Estate Master Pty Ltd
Installation and Configuration
19
4. If a suitable location to backup the database is selected, the database will backup to a *.bak file
and the user will be notified.
5. Click 'OK' and the database upgrade will commence.
6. Once the upgraded has been completed, click 'Close' on the progress screen and the Upgrade
status on the home page will be refreshed.
© 2011 Estate Master Pty Ltd
20
2.5
Estate Master Enterprise Database
Backup the Database
At any time, any user of the Enterprise Database can conduct a backup of the database using the
Management Tool.
Access Denied Error
If an 'Access Denied' error message appears when trying to create, backup or restore the Estate
Master Enterprise Database, the user may not have the proper permissions within SQL to ‘create a
database’.
To adjust these permissions, please refer to the Advanced Instructions
1. To conduct a backup, the user must ensure that the database is up to date. If it needs to be
upgraded, then a database backup cannot be performed until such time. If the database does
need to be upgraded, a mandatory backup will be conducted before the upgrade can occur.
2. Once the database is up to date, the user will be able to conduct a backup of the database.
Click 'Backup' to commence the process.
3. Select a location and enter in a filename and click 'Save'.
© 2011 Estate Master Pty Ltd
Installation and Configuration
21
4. You can only backup to the same server as where the database is located. If you try to backup
to another machine, you will get the following error message and you will need to attempt to
backup again.
5. If a suitable location to backup the database is selected, the database will backup to a *.bak file
and the user will be notified.
6. Once backup has been completed, a message will display the file name and the main screen of
the Management Tool will display date and time of the last backup and who conducted it.
© 2011 Estate Master Pty Ltd
22
2.6
Estate Master Enterprise Database
Restore the Database
Once a backup of the Enterprise Database is undertaken, the user can restore it using the
Management Tool if the live version is:
· Accidentally deleted or deleted from a system/hard drive failure.
· Corrupted.
· The user needs to revert the data back to a point in time.
· The user needs to move the database from one server to another.
1. To conduct a Restore:
· The user must have a valid and exclusive connection to the Enterprise Database.
· If on a Windows Domain, then the user must be a member of the Domain Admin group.
· If not on a Windows Domain, then the user must be a member of the Local Admin group
· The user must have SQL permissions to restore the database.
2. Click [Restore] and the program will prompt the user to select an archived version of the
Enterprise Database (*.bak file). Select the relevant file to restore and click [Open].
© 2011 Estate Master Pty Ltd
Installation and Configuration
23
3. The program will then ask the user if they wish to continue with the restore. Click [Yes] to
continue or [No] to abort the restore process.
4. The program will then warn the user that they are about to overwrite the database. Click [Yes] to
continue or [No] to abort the restore process.
5. The restore process will then begin. If the selected file is not a valid Enterprise Database file (*.
bak file), then a message will appear.
6. Once the restore process is successful, a message will appear.
© 2011 Estate Master Pty Ltd
Part
III
Using the Enterprise Database with Estate Master
3
Using the Enterprise Database with Estate Master
3.1
Preparing Data for Exporting
25
The Estate Master Enterprise Database is a powerful data repository and a robust framework for high
level reporting. It is therefore recommended that the data that is exported to it is accurate and
meaningful.
Before exporting your Estate Master DF, DM or IA cash flow into the Enterprise Database, please
ensure that the following key areas are set:
Intro Sheet
1. Project Introduction (Estate Master DF and DM)
This is information that will be used in the Enterprise Database to identify your Project, please
insure it is completed. The 'Project Number' and 'Project Title' are distinctive: This will be the most
unique identifier of this Project that the cash flow belongs to. Any cash flows with the same Project
Number and Project Name will grouped together in the Enterprise Database.
Estate Master DF and DM cash flows
2. Project Introduction (Estate Master IA)
This is information that will be used in the Enterprise Database to identify your Project, please
insure it is completed. The 'Project Number' and 'Project Name' are distinctive: This will be the
most unique identifier of this Project that the cash flow belongs to. Any cash flows with the same
Project Number and Project Name will grouped together in the Enterprise Database.
The 'Property Name' is what distinguishes the cash flows within the same project, so please
ensure that this is unique compared to other cash flows in that project.
The 'Type', 'Status' and 'Valuation Date' fields will also be referenced in the Enterprise Database
and used as search filters, so please take note of your choices and update them accordingly.
© 2011 Estate Master Pty Ltd
26
Estate Master Enterprise Database
Estate Master IA cash flows
Input/Setup Sheets
1. Options/Stages (Estate Master DF)
In DF, you can only export cash flows that have been stored as Options/Stages. You will note, DF
will not allow you to store any cash flows as Options/Stages if they have the same Cash Flow Title
in the Input/Setup Sheet. The Cash Flow Title is what distinguishes the cash flows within the same
project, so please ensure that this is unique compared to other cash flows (e.g. options, stages,
etc) in that project.
2. 'Type' and 'Status' Fields (Estate Master DF and DM)
The Type and Status fields will also be referenced in the Enterprise Database and used as search
filters, so please take note of your choices and update them accordingly.
© 2011 Estate Master Pty Ltd
Using the Enterprise Database with Estate Master
27
3. Revenue Data (Estate Master DF and DM)
For more feature-rich and detailed reporting, it is advised that revenue data is entered in detail and
categorised using the 'Land Use Codes'.
Easier data entry, but lacks detail !
Recommended Option: More input detail leads to more meaningful and effective reporting.
© 2011 Estate Master Pty Ltd
28
3.2
Estate Master Enterprise Database
Exporting to the Database
To export all the input data in your Estate Master DF/DM/IA file to the Enterprise Database, follow
these steps:
1. Ensure that the relevant Project Details are entered in the Intro sheet of the DF/DM/IA file.
Estate Master DF and DM cash flows
Estate Master IA cash flows
2. Either through the Estate Master Menu or the Toolbar, click on the 'Export to Enterprise
Database' button
.
3. If exporting from Estate Master DF, the program will detect if the current set of Inputs has been
stored as an Option/Stage. If it hasn't, a prompt will appear, requesting the user to store the
current set of data in the Input sheets before proceeding. Only stored Options/Stages can be
exported to the Enterprise Database.
4. If the database configuration file (EMDB.ini) is not found on the system (and hence a connection
to the Enterprise Database cannot be established), then the following error message will
appear. It will prompt the user to run the Enterprise Database Management Utility to assist in
setting up a connection. Please refer to the Setup and Connect to the Database section for
more information about configuration.
5. Once the connection is successful, an Export Wizard will appear.
Step 1 - Export Cash Flows (when exporting DF files only)
1. Step 1 applies only to Estate Master DF users, DM and IA users; please go straight to Step 2.
The first step of the process prompts the user to select what they would like to export (this step
© 2011 Estate Master Pty Ltd
Using the Enterprise Database with Estate Master
29
applies to DF files only):
· Export All: Exports all options in the DF file, 1 through to 8.
· Export Individually: Allows the user to select which specific options in the DF file to export.
2. Once selected, click 'Next'.
Step 2 - Project Allocation
1. Using the Project Name and Project Number on the Intro sheet of the DF/DM/IA file, it will
attempt to find any records of that 'Project Name' or 'Number' in the database. If the project is
already in the database, it will skip Step 2 and continue to Step 3. Otherwise, the following
messages may appear on the wizard:
· It is the first Project to be created in the database
· Project Number and Name Doesn't Exist
· There is a mismatch between the details on the file and in the database
2. If any of these messages appear, two options are available to the user:
· Add New Project to Database: If this option is selected, by default, it will use the details on
the Intro sheet of the DF/DM/IA file as the Project Number and Name. The user can edit this
if necessary directly in the wizard, and the Intro sheet will be automatically updated.
© 2011 Estate Master Pty Ltd
30
Estate Master Enterprise Database
· Append to Existing Project: If this option is chosen, the Project Number and Name fields
are disabled, and the user is required to select a project that is already in the database.
Once selected, the Intro sheet will be automatically updated.
Step 2 - Confirm Export Details
1. If the project is already in the database, it will go then the following messages may appear. The
user has the ability to change the project the cash flow is being exported to if required. It will
also inform the user if this is a new cash flow being exported, or if the cash flow already exists in
the database.
Step 3 - Export Data
1. Once satisfied with the details, click 'Export' to begin the data transfer process.
© 2011 Estate Master Pty Ltd
Using the Enterprise Database with Estate Master
3.3
31
Importing from the Database
To import input data in your Estate Master DF/DM/IA file from the Enterprise Database, follow these
steps:
1. Either through the Estate Master Menu or the Toolbar, click on the 'Import from Enterprise
Database' button
.
2. If the database configuration file (EMDB.ini) is not found on the system (and hence a connection
to the Enterprise Database cannot be established), then the following error message will
appear. It will prompt the user to run the Enterprise Database Management Utility to assist in
setting up a connection. Please refer to the Setup and Connect to the Database section for
more information about configuration.
3. Once the connection is successful, an Import Wizard will appear.
Step 1 - Select Project
1. The first step will display a list of the Projects that exist in the Enterprise Database. If their is an
extensive list, you can filter it either by Project Number or Name.
2. Select the appropriate project and click on 'Next'.
© 2011 Estate Master Pty Ltd
32
Estate Master Enterprise Database
Step 2 - Select Cashlow
1. The next step will display all the cash flows that exist in the selected Project in the database.
You can sort the list by clicking on the column headers.
2. In the 'Import' column, select the cash flows you wish to import. Once selected, click 'Next'.
· DF: There is a maximum of 8 cash flows you can import into a DF file from the database.
· DM: There is a maximum of 1 cash flows you can import into a DM file from the database.
· IA: There is a maximum of 1 cash flows you can import into a IA file from the database.
Step 3 - Select Stage/Option (when importing DF files only)
1. This step applies to DF users only, DM and IA user please go straight to Step 4.
The next step will allow the user to allocate the cash flows they wish to import to the relevant
Stage/Option in the DF file they are importing into.
Step 4 - Import
1. Once satisfied with the details, click on 'Import' to begin the file transfer process.
© 2011 Estate Master Pty Ltd
Using the Enterprise Database with Estate Master
3.4
Exporting Reminders
Reminding Estate Master Users to Export
DF Users: When storing Options/Stages in a DF
model, the user may be prompted each time to also
store the cash flow into the Enterprise Database at
that point in time.
If the user clicks 'No', then if they ever need to
export to the Enterprise Database, it must be done
manually through the Estate Master Menu or
Toolbar.
DM Users: When setting the Original, Project or
Previous Budgets in a DM model, the user may be
prompted each time to also store the budget into
the Enterprise Database at that point in time.
If the user decides to export and clicks 'Yes', then
data export wizard will appear, and once all data is
exported into the database, the cash flow will be
mark it accordingly in the database with the budget
type (ie Previous Budget, Original Budget, etc).
If the user clicks 'No', then if they ever export to the
Enterprise Database manually through the Estate
Master Menu or Toolbar in DM, then the cash flow
will be marked as 'Current Budget' in the cash flow.
To select whether or not you wish these prompts to
always appears when setting budgets (DM) or
storing options/stages (DF), go to the General tab of
the Estate Master Preferences for DF or DM.
© 2011 Estate Master Pty Ltd
33
Part
IV
Advanced Instructions
4
Advanced Instructions
4.1
SQL Express 2008 Installation Guide
35
The Estate Master Enterprise Database can be run on two types of SQL servers.
· SQL Server (Licensed Version)
· SQL Express (Free Distributable Version)
The free SQL Server Express Editions have limitations on database size, so for larger enterprises, we
recommend using Workgroup, Standard or Enterprise Editions. For more information visit the SQL
Server 2008 Editions website.
The following instructions cover the recommended installation and configuration of SQL Server
Express for use of Estate Master. Installation of SQL Server will be very similar, with a few minor
differences.
Important Information
Please inform your IT or Database Administrators before attempting to install SQL on your system.
It is recommeded that you check with them to see if any existing instances of SQL Server are
installed on your network and can be used for the Estate Master Enterprise Database.
1. Please download the following programs:
Platform Database (Required)
Management Tools (Optional) *
32-bit
http://go.microsoft.com/?linkid=9729742 http://go.microsoft.com/?linkid=9729744
64-bit
http://go.microsoft.com/?linkid=9729743 http://go.microsoft.com/?linkid=9729745
* Optional. The Management Tools (SQL Server Management Studio Express), are a graphical management tool
based on SQL Server Management Studio that makes it easy to manage and administer SQL Server Express
databases.
2. Run the SQL Server 2008 Express setup, which is downloadable from the link above. This will
start the ‘SQL Server Installation Centre’
© 2011 Estate Master Pty Ltd
36
Estate Master Enterprise Database
3. Clink on 'Installation'
4. Click ‘New SQL Server stand-alone installation or add features to an existing installation’
© 2011 Estate Master Pty Ltd
Advanced Instructions
37
5. If all ‘Setup Support Rules’ have passed, click ‘OK’.
6. Click ‘Next’ when the installation asks you to specify the edition of SQL being installed. Because
the edition is Express it will be automatically selected and disabled.
© 2011 Estate Master Pty Ltd
38
Estate Master Enterprise Database
7. Click the check box to accept the licensee terms and click 'Next'.
8. Click ‘Install’ to install any files needed by the SQL installation.
© 2011 Estate Master Pty Ltd
Advanced Instructions
39
9. Please wait as any support files are installed. Click ‘Next’ after any support files have been
installed.
10.Select the ‘Database Engine Services’ check box and click ‘Next’
© 2011 Estate Master Pty Ltd
40
Estate Master Enterprise Database
11.Enter a named instance or accept the default, then click ‘Next’.
IMPORTANT: This instance name will be used by Estate Master when creating and
configuring a connection to the Estate Master Enterprise database
12.Click ‘Next’ if there is sufficient hard disk space to continue the installation.
© 2011 Estate Master Pty Ltd
Advanced Instructions
41
13.Click ‘Next’ on the Server Configuration screen.
14.Click ‘Add Current User’ to add the current user to the SQL Server Administrators group and
click ‘Next’
IMPORTANT: At least one Windows account must be added to the SQL Server Administrators
for the installation to continue.This will allow the current user to create the Estate Master
Enterprise database on this machine.
© 2011 Estate Master Pty Ltd
42
Estate Master Enterprise Database
15.Choose to participate in SQL Error and Usage Reports as you wish, and click ‘Next’.
16.Once the installation rules have completed click ‘Next’.
© 2011 Estate Master Pty Ltd
Advanced Instructions
17.The SQL installer will now start when you click ‘Install’. Please wait while SQL Express is
installed
18.SQL should complete successfully install all components. Click ‘Next’.
© 2011 Estate Master Pty Ltd
43
44
Estate Master Enterprise Database
19.Click ‘Close’ to complete the installation.
20.Close the ‘SQL Server Installation Centre’.
© 2011 Estate Master Pty Ltd
Advanced Instructions
4.2
45
Permission Requirements
Permissions for Using the Enterprise Database
The following is a breakdown of specific minimum permissions required in SQL to use the Enterprise
Database once it has been set up:
Basic User (Exporting and Importing)
· Insert, Edit, and Delete permissions in Tables and Views
· Execute permissions on Procedures and Functions
Admin User (Exporting, Importing and Database Upgrades)
· Insert, Edit, and Delete permissions in Tables and Views
· Execute permissions on Procedures and Functions
· Modify permissions on Objects (Tables, Stored Procedures, etc)
Permissions for Backing Up a Database
In order to backup a database, the user needs to have the proper permissions.
For example, if there are insufficient permissions while a user is trying to backup a database, they may
get the following error message:
These permissions need to be adjusted in SQL.
1. Go to Start > Control Panel > Administrative Tools.
© 2011 Estate Master Pty Ltd
46
Estate Master Enterprise Database
2. Double click 'Services'.
3. Double click on SQL Server (SQL Express).
4. Click the ‘Log On’ tab and click the option 'Local System Account' and then click OK.
5. Restart the service by selecting SQL Server (SQLExpress) and then clicking ‘Restart’.
© 2011 Estate Master Pty Ltd
Advanced Instructions
4.3
47
SQL Replication
If there are multiple offices within an organisation that each house a server, an option may be to install
the Estate Master Enterprise Database at each location and then synchronise it with a main central
server using SQL Replication. This will allow users to connect to their own local Enterprise Database
over a LAN and then have it synchronise over a WAN to the main database when there is less
bandwidth activity (ie after hours).
SQL Replication is a set of technologies for copying and distributing data from one database to
another and then synchronizing between databases to maintain consistency. Using replication, you can
distribute Estate Master data to different locations, ideal for organisations that have many Estate
Master users across multiple locations.
Types of Replication
Microsoft SQL Server provides the following types of replication for use in distributed applications,
such as the Estate Master Enterprise Database:
· Snapshot Replication
o The simplest type of replication.
o Commonly used to provide the initial set of data and database objects.
o Ideal when data changes infrequently, replicating small volumes of data, or changes are
substantial but infrequent.
o It takes an entire database, sends it to another server’s database, overwriting the current
data.
o It doesn’t overwrite the whole database, just the data from the initial database.
· Transactional Replication
o Typically used in server-to-server environments.
o Ideal when incremental changes to be propagated as they occur.
o This type also takes a Snapshot, but after that replicates only the changed data from one
system to another.
· Merge Replication
o Typically used in server-to-client environments
o Ideal when many users update the same data at various times and propagate those
changes to other databases/users.
o Ideal when users need to receive data, make changes offline, and later synchronize
changes.
o This takes a comparison between two databases and then transfers the differences
between them.
o You have the option of making one server the winner of any conflicts, or of having those
conflicts stored so that you can resolve them manually.
The type of replication you choose for the Enterprise Database depends on many factors, including the
physical replication environment, the type and quantity of data to be replicated, and how the data is to
be updated.
For more information on how to setup and configure SQL Replication for the Estate Master Database,
please refer to Microsofts MSDN website for documentation and tutorials: http://msdn.microsoft.com
© 2011 Estate Master Pty Ltd
Part
V
Licence Agreement
5
49
Licence Agreement
1.
Acceptance of Terms
1.1 Permission to use this Software is conditional upon you reading and accepting all the terms of this licence
agreement. By clicking "I Accept", you accept all of the terms. If you do not wish to accept the terms, you must not
click “I Accept” and you may not use the Software.
1.2 If you are using the Software on behalf of a company or an organisation, in clicking the “I Accept” button during
installation you warrant that you are authorised by the company or organisation to agree the terms on its behalf.
2.
Licence
2.1 We grant you a non-exclusive, non-transferable licence to use:
(a) the Software, on equipment owned and used by you at the Site:
(i)
on the number of computers equal to the number of User/PC Licenses that you have purchased; or
(ii) by the number of concurrent users equal to the number of CAS Licences that you have purchased; and
(b) the Documentation,
on the terms of this agreement.
2.2 You acknowledge that there is no transfer to you of any right in the Software or the Documentation other than the
licence granted in clause 2.1.
3.
Your obligations
3.1 You must not and must not allow any other person to:
(a) except as expressly permitted by law, copy, alter, modify, tamper with, decompile, reverse engineer or attempt
to reverse engineer, the Software, or use the Software to develop other software;
(b) copy the Documentation;
(c) permit the Software to be combined with or incorporated in other software; or
(d) use the Software to supply hosting services or bureau services to any person.
3.2 You must:
(a) use the Software only in accordance with the Documentation;
(b) ensure that the Software is used only by people trained to use it;
(c) establish and carry out reasonable backup procedures for the Software;
(d) comply with our support and operating procedures current from time to time; and
(e) comply with all reasonable directions issued by us regarding use of the Software.
3.3 You must keep records in sufficient detail to enable compliance with your obligations under this agreement to be
verified. We, or our auditors, after giving you at least 48 hours notice may examine your records during your usual
business hours to verify that you have complied, and are complying, with those obligations.
3.4 You indemnify us and our officers, employees and agents from and against any loss (including reasonable legal
costs and expenses) or liability reasonably incurred or suffered by any of those indemnified where such loss or
liability was caused by:
(a) your breach of your obligations under this agreement; or
(b) your wilful, unlawful or negligent act or omission.
4.
Evaluation Period and Activation
4.1 You may use the Software for the purpose of evaluation for a period of up to 30 days from the date of installation of
the Software. After the evaluation period has expired, you must either:
(a) input an activation key and register the Software in accordance with the installation and registration
instructions provided with the Software; or
(b) stop using the Software and uninstall it so that it is deleted from all computer equipment.
4.2 If, after evaluation, the Software is not registered in accordance with clause 4.1(a),
(a) the licence granted in clause 2.1 terminates; and
(b) the Software will disable itself and become unusable.
4.3 The Software is matched to the computer equipment on which the Software is first activated for use and the
Software will disable itself and become unusable if you attempt to use it on another computer. However, on request
we will issue a further activation key to you to allow you to install the Software on another computer, provided that
you satisfy us that you have uninstalled the Software from the original computer.
© 2011 Estate Master Pty Ltd
50
Estate Master Enterprise Database
5.
Documentation
You acknowledge that the Documentation contains sufficient information for the adequate use of the Software, except to
the extent we have notified you of any omission or deficiency or of any variation that we consider necessary for the proper
use of the Software.
6.
Initial and Ongoing Fees
6.1 You must pay the Licence Fee and the Support Fee for the first 12 months in accordance with our standard
payment requirements before we will issue an activation key for the Software.
6.2 If you dispute any invoice, you must pay any undisputed amount and must notify us in writing within seven days
after receipt of the invoice of the reason for the dispute. The dispute will then be dealt with under clause 16. If the
outcome of the dispute resolution process is that some or all of the disputed amount should properly have been
paid, you must pay that amount together with interest at the rate prescribed from time to time for unpaid judgments
of the Supreme Court of NSW, calculated from the original due date.
6.3 All fees, charges and other amounts referred to in this agreement are exclusive of Government Charges.
6.4 If any supply under this agreement is a taxable supply or results in Government Charges, the party making the
supply:
(a) may, in addition to any payment for the supply, recover the amount of the Government Charges applicable to
the supply; and
(b) must issue a tax invoice to the recipient within 28 days after making the taxable supply.
7.
Security
You are responsible for the use, supervision, management and control of the Software and Documentation. You must
ensure that the Software is protected at all times from misuse or any form of unauthorised use.
8.
Support Services, Upgrades and New Releases
8.1 Except to the extent specified in this agreement, we are not obliged to support the Software, whether by providing
advice, training, error-correction, modifications, upgrades, new releases or enhancements or otherwise.
8.2 We will provide support for the Software for a period of 12 months after the date of activation. After 12 months,
support is available on our standard terms on payment of the Support Charge. Our standard terms for support are
available on our website.
8.3 If we offer an upgrade or new release and you accept:
(a) the charge for the upgrade or new release will be at our then current rate for existing customers;
(b) this agreement will continue to apply to the upgrade or new release; and
(c) you must return to us all copies of the original Software or otherwise deal with all copies of the original
Software in accordance with our directions.
9.
Software performance
9.1 We do not guarantee that the Software is or will be error free for all possible systems, combinations of software and
input variations.
9.2 It is a condition of this agreement that you test the Software for compatibility with your systems, existing software
and input permutations. You must audit the output results of the Software on a regular basis to ensure the ongoing
suitability and integrity of the Software.
10. Warranty
10.1 We warrant that:
(a) for the duration of the Warranty Period, the Software will operate in conformity with the Documentation in all
material respects;
(b) the Software and Documentation does not infringe the Intellectual Property Rights or moral rights of any
person; and
(c) we have all necessary rights to grant the licence under clause 2.1.
10.2 If, during the Warranty Period, you consider there is a defect in the Software such that the Software does not
conform with, or cannot be used in accordance with, the Documentation, you must notify us. We will investigate any
defects so notified and, upon verification of the existence of the defect, rectify the defect without additional charge to
you.
11. Limitation of Liability
11.1 You acknowledge that:
(a) the Software or the Documentation may contain errors or inaccuracies;
© 2011 Estate Master Pty Ltd
Licence Agreement
51
(b) results produced by the Software may contain errors or inaccuracies; and
(c) you rely on your own professional skill and judgement in using the Software and in determining its suitability for
any purpose.
11.2 We do not exclude or limit the application of any provision of any statute (including the Trade Practices Act 1974)
where to do so would contravene that statute or cause any part of this agreement to be void, including any provision
implying any condition, warranty or providing for an indemnity. In this clause an implied condition or warranty the
exclusion of which from a contract (including a contract with a consumer as defined in the Trade Practices Act 1974)
would contravene any statute or cause part or all of this clause to be void is called a Non-excludable Condition.
11.3 Our total liability to you for a breach of any express term of this agreement, or for a breach of any Non-excludable
Condition (other than one implied by section 69 of the Trade Practices Act 1974), is limited, at our option, to any one
of supplying, replacing or repairing, or paying the cost of supplying, repairing, or replacing the goods or supplying
again, or paying the cost of supplying again, the services in respect of which the breach occurred.
11.4 We exclude:
(a) from this agreement all conditions, warranties and terms implied by statute, general law or custom, except any
Non-excludable Condition;
(b) except for liability in relation to a breach of a Non-excludable Condition, all liability to you in contract for
consequential or indirect damages arising out of or in relation to the Software or Documentation, any delay or
other failure in supplying the Software or Documentation, even if we knew they were possible or they were
otherwise foreseeable, including lost profits and damage suffered as a result of claims by any third person;
and
(c) all liability in negligence.
12. Confidentiality
12.1 Each party:
(a) may use Confidential Information of the other party solely for the purposes of this agreement;
(b) except as permitted under clause 12.1(c), must keep confidential all Confidential Information of the other party;
and
(c) may disclose Confidential Information of the other party only:
(i) to persons who:
(A) are aware and agree that the Confidential Information of the other party must be kept confidential;
and
(B) either have a need to know (and only to the extent that each has a need to know), or have been
specifically approved by the other party; or
(ii) as required by law or stock exchange regulation.
12.2 Even though information is the Confidential Information of a party, the other party is not obliged to comply with
clause 12.1 in relation to that Confidential Information if:
(a) the Confidential Information has become public knowledge; or
(b) the other party became aware of that Confidential Information from a third person,
in circumstances where there was no breach of any obligation of confidence.
12.3 You must not make any public statement:
(a) about the performance of;
(b) about the operation of; or
(c) benchmarking,
the Software without our prior written consent.
13. Intellectual Property Rights
13.1 In the event that proceedings are brought or threatened by a third party against you alleging that your use of the
Software constitutes an infringement of Intellectual Property Rights, we may at our option and own expense conduct
the defence of such proceedings. You must provide all necessary co-operation, information and assistance to us in
the conduct of the defence of such proceedings.
13.2 If the Software is found to infringe a third party’s Intellectual Property Rights, we may at our option:
(a) procure for you the right to continue using the Software;
(b) modify the Software so that it becomes non-infringing; or
(c) replace the Software with other software with similar functionality.
14. Term and Termination
14.1 This agreement continues until:
© 2011 Estate Master Pty Ltd
52
Estate Master Enterprise Database
(a) a party terminates the agreement in accordance with clause 14.2; or
(b) you give us at least 30 days notice.
14.2 A party may terminate this agreement with immediate effect by giving notice to the other party if:
(a) that other party breaches any material term of this agreement not capable of remedy;
(b) that other party breaches any material term of this agreement capable of remedy and fails to remedy the
breach within 30 days after receiving notice requiring it to do so; or
(c) any event of insolvency happens to that other party (whether or not notified).
15. On Termination
15.1 On termination of this agreement other than for our breach or insolvency, the licence granted under clause 2.1
terminates and you must immediately:
(a) stop using the Software;
(b) return to us all copies of the Software and Documentation in your possession or control; and
(c) ensure that all of the Software has been deleted or permanently removed from any equipment on which it is
stored.
15.2 You acknowledge that if this agreement is terminated other than for our breach or insolvency, in addition to any
other remedies we may have, we may:
(a) retain all fees paid under this agreement;
(b) charge a reasonable sum for work performed in respect of which work no sum has been previously charged;
and
(c) if you do not return to us all Software and Documentation in your possession or control in accordance with
clause 15.1, at your cost, enter any of your premises during working hours to repossess them.
16. Dispute Resolution
16.1 Neither party may start arbitration or court proceedings (except proceedings seeking interlocutory relief) in respect
of a Dispute unless it has first complied with this clause.
16.2 A party claiming that a Dispute has arisen must notify the other party within 10 working days after the event
occurring that has given rise to the Dispute.
16.3 Within 7 working days after a notice given under clause 16.2 each party must nominate in writing to the other party a
representative authorised to settle the Dispute on its behalf.
16.4 During the 20 working day period after a notice is given under clause 16.2 (or if the parties agree a longer period,
that longer period) each party must use his or her best efforts to resolve the Dispute.
16.5 If a Dispute is not resolved within that time, the Dispute must be referred:
(a) for mediation, in accordance with the Australian Commercial Disputes Centre (ACDC) Mediation Guidelines;
and
(b) to a mediator agreed by the parties, or if the parties do not agree on a mediator, a mediator nominated by the
then current chief executive officer of ACDC or the CEO’s nominee (or if no such person is available or willing
to nominate a mediator, by the then President of the Law Society of New South Wales).
17. Force Majeure
17.1 Neither party is liable for any delay or failure to perform its obligations pursuant to this agreement if such delay is
due to Force Majeure.
17.2 If a delay or failure of a party to perform its obligations is caused or anticipated due to Force Majeure, the
performance of that party's obligations will be suspended.
17.3 If a delay or failure by a party to perform its obligations due to Force Majeure exceeds sixty days, either party may
immediately terminate the agreement on providing notice in writing to the other party.
17.4 If this agreement is terminated pursuant to clause 17.3, we will refund moneys previously paid by you for any goods
or services not supplied to you.
18. Entire Agreement
This agreement, including the Invoice, constitutes the entire agreement between the parties and supersedes all prior
representations, agreements, statements and understandings, whether verbal or in writing.
19. Assignment
You may not assign the benefit of this agreement without our written consent.
© 2011 Estate Master Pty Ltd
Licence Agreement
53
20. Variation
This agreement may be varied only by a document signed by both parties that states expressly that it varies this
agreement.
21. Severability
If any provision of this agreement is held invalid, unenforceable or illegal for any reason, the agreement remains
otherwise in full force apart from such provision, which is deemed to be deleted.
22. Governing law
22.1 This agreement is governed by the law applicable in New South Wales, Australia and each party irrevocably and
unconditionally submits to the non-exclusive jurisdiction of the courts of that State.
23. Notices
23.1 Notices under this agreement must be in writing and may be delivered by hand, by mail or by facsimile to the
addresses specified on the Invoice.
23.2 Notice will be deemed given:
(a) in the case of hand delivery, upon written acknowledgment of receipt by an officer or other duly authorised
employee, agent or representative of the receiving party;
(b) in the case of posting, three days after dispatch;
(c) in the case of facsimile, upon receipt of transmission if received on a business day or otherwise at the
commencement of the first business day following transmission.
24. Definitions
24.1 The following definitions apply unless the context requires otherwise:
CAS License means Client Access Session, being the number of users that can use the Software at any one time on a
network via a terminal server. For example, 20 people might have access to use the Software via a terminal server
network, but a single CAS means that only one may use it at a time.
Confidential Information of a party means all confidential information (including trade secrets and confidential know
how) relating to that party or a corporation related (as that term is used in the Corporations Act 2001 (Cth)) to that party
from time to time, of which the other party becomes aware.
Documentation means any operating manuals and other printed materials including users' manuals, programming
manuals, modification manuals, flow charts, drawings and software listings that are designed to assist or supplement the
understanding or application of the Software.
Force Majeure means a circumstance beyond the reasonable control of the parties which results in a party being unable
to observe or perform on time an obligation under this agreement. Such circumstances include:
(a) acts of God, lightning strikes, earthquakes, floods, storms, explosions, fires and any natural disaster;
(b) acts of war, acts of public enemies, terrorism, riots, civil commotion, malicious damage, sabotage and
revolution; and
(c) strikes.
Government Charges means any taxes, duties or government charges arising out of or in connection with entering into
this agreement or making a supply under it, including GST.
Intellectual Property Rights means all intellectual property rights, including:
(a) patents, copyright, rights in circuit layouts, registered designs, trade marks and the right to have confidential
information kept confidential; and
(b) any application or right to apply for registration of any of those rights.
Invoice means our invoice received by you in relation to this agreement.
Licence Fee means the fee specified on the Invoice, payable to us for the use of the Software.
Software means the software specified on the Invoice that you are licensed to use under this agreement, including any
enhancement, modification, upgrade or new release of that software.
Site means the physical address for the use of the Software specified at the time of installing the Software.
Support Charge means a charge for support in accordance with our standard rates in effect from time to time.
User/PC License means the licence for a single person to install, register and operate the Software on a single
computer.
Warranty Period is the period of 90 days from the date of installation of the Software.
We, including its different grammatical forms such as our and us, means Estate Master Pty Limited, ABN 76 102 232
593, of Level 6, 234 George Street, Sydney, NSW, Australia.
© 2011 Estate Master Pty Ltd
54
Estate Master Enterprise Database
You means the person installing the software or, where it has been installed on behalf of a company or organisation
under clause 1.2, that company or organisation.
24.2 The following rules of interpretation apply unless the context requires otherwise:
(a) any use of the verb includes, or of words such as for example or such as, do not limit anything else that is
included in general speech; and
(b) unless otherwise stated, monetary references are references to Australian dollars.
© 2011 Estate Master Pty Ltd
">