To make sure you have the latest edition of Crows Nest Software, you'll need to periodically download and install updates from our release notes page.
Determine if database update is required
Open your current version of Crows Nest and check the Database Version date. This can be seen on the Login window, or if already logged in under Help-->About. Compare this with the date the Database Version date listed in the email sent out with the update or on our downloads page. If the Database Version is different, continue to the section just below titled ‘Install and Update Database(s)’. If they are the same, you can just install on the server or any workstation and login to the database. This will trigger the auto-update mentioned in Installing Update on Client PCs below.
Install and update database(s)
To complete this step you must have access to credentials for an account that has permission to modify the database and create logins in the SQL Server. Either the current Windows user must be granted these permissions, or you can enter credentials for a Windows or SQL Server account with the necessary permissions.
When a database update is in progress, the client application will automatically logout and block others from accessing to the database while the update is in progress. When the update is finished, the clients can connect again.
Log onto the PC running SQL Server.
Install the Crows Nest update using the file "CrowsNestSetup.msi". When installing, ensure DB Utility is selected on the Custom Setup step (see pics below)
Open the application "Crows Nest DB Utility.”
Fill in the "Server" and "Database" fields to point to your SQL Server instance. The "Refresh List" buttons can be used to find SQL Servers on the network and query Database names from the selected server.
Either check the "User current Windows login" option or enter credentials for another account with permission to modify the database.
Click the button titled "Update Database"
Answer "Yes" when prompted to Backup the Database
Use the folder selection window that opens to select a backup location. Backing up to a User's folder such as the Desktop or My Documents won't work unless specific permissions are granted to the folder. In most network situations, creating a folder in the root folder of the local drive will work. To configure a specific folder with permissions, first figure out which account is configured to run the SQL Server service. You can see this by viewing "Services" in Windows, finding the service for the SQL Server instance, and reading the account listed in the "Log On As" column. With most SQL Server versions using the default options for installation will create a new user account to run the service. (Example: MSSQL$ServerInstanceName). A default folder should be created with the correct permissions when the SQL Server instance is installed and can typically be found here: C:\Program Files\Microsoft SQL Server<Instance Name>\MSSQL\Backup
After the Backup has completed, click "OK" to continue to update the database.
If you use multiple databases, repeat steps 4 through 9 for each database.
Close the DB Utility application. Next, move to Installing Update on Client PCs below.
Install update on client PCs
Auto-Update
When a user attempts to connect to a database it will check to see if a client has connected with a newer version or if a database update has been run with a newer client version. If either of these conditions are true, it will see if there is a file path for the install file stored in "Install File Location" setting under Settings-->Options-->General Tab (see following pic). If it finds a valid file path there it will prompt the user to run it. Make sure the path can be reached by all clients by using a network UNC path or a mapped drive location shared by all clients.
Manual Update
Install the file "CrowsNestSetup.msi" on each client PC manually. There are ways to distribute an install file to multiple PCs on a network from a single location. Consult your IT professionals for options.
