AB Sciex is doing business as SCIEX. © 2010-2018 AB Sciex. The trademarks mentioned herein are the property of the AB Sciex Pte. Ltd. or their respective owners. AB SCIEX™ is being used under license. Beckman Coulter® is being used under license. Product(s) may not be available in all countries. For information on availability, please contact your local representative. For research use only. Not for use in diagnostic procedures.
For research use only. Not for use in diagnostic procedures.
Section A relates to the Authentication or how access is granted to the server. What you choose here very much depends on your type of network. If you have an Active Directory network with your instruments attached and you want to manage the permissions to upload and read data using your domain active directory then Windows authentication mode may be quick and easy for you to setup. However this setting will rely on help from your active directory administrators in order to maintain. If you do not meet all of the criteria above or you do not know we would suggest choosing Mixed Mode in Section A. Once you choose Mixed mode you will be asked to enter a password for the (sa) user. This is like an Administrator Account for the database. In this instance I have entered “!DQO30”.
Section B Defines the additional administrator users for the system. Unless your IT dept has a specific requirement for this leave it as default (the installing user account). Once Complete Click ‘Next >’
Set Enabled to Yes and click ‘Apply’.
Click OK to Close the Warning and OK to close the properties window.
The service will restart.
Once completed you can close the Sql Server Configuration Manager.
This will open what looks like a code window. This is the SQL code used to make the Database for DiscoveryQuant.
There are 2 Files that are created for Any SQL Database. The locations of these are hardcoded at the top of the script. If you are installing this Database on a dedicated server i.e IT DOES NOT HAVE DISCOVERYQUANT 3.0 INSTALLED you will need to create a directory of C:\DiscoveryQuant30 on the computer as this is where the files are stored. THE SCRIPT WILL FAIL IF THIS DIRECTORY IS NOT CREATED
Back in SQL Management Studio, to build the Database simply click Execute.
In the Messages Section you should see the Message ‘Command(s) completed successfully’
Enter a login name (A) (can be anything you want but following the guide will help if anything goes wrong) I have used ‘DiscoveryQuant’, select SQL Server authentication and add a password (B)(I have used !DQO30). Uncheck Enforce password policy (C) and change Default database to ‘DiscoveryQuantv30’(D).
Swich to User Mapping in the Select a Page Section and check Map checkbox next to DiscoveryQuantv30. Check db_owner in the roles at the bottom of the pane and click OK.
The Database setup is now complete so we need to test the access of the user to ensure that the clients will be able to connect. Close down the SQL Server Management Studio window.
Once you get a ‘New Text Document.txt’ (note very important you see the .txt – if you don’t you need to change folder options to show known extensions) right click and select Rename. Change the name to ‘LocalConnection.udl’ Windows will give a warning about changing file extension – Click Yes. Your icon should change to this.
Right click on the udl file and Select Properties
On the Provider Tab Select ‘Microsoft OLE DB Provider for SQL Server’
The Connection Tab - Section 1. – Pressing Refresh should find all available instances of SQL server. However I have not found this completely reliable in all environments. The format should be <LOCAL COMPUTER NAME>\<SQL INSTANCE NAME> so if you have followed this guide completely your ComputerName\DISCOVERYQUANT30 should work (and you can just type it in the box).
In Section 2. If you have used Active Directory Security you can Select ‘Use NT Integrated Security’ or if you have not Select Use a specific user name and password and Enter the details you provided in step 19. Check Allow saving password. For Section 3. Click the dropdown for Select the database on the server. At this point it will give an error if anything is wrong – if not it will list the databases, assuming it does select DiscoveryQuantv30 and press ‘Test Connection’. Hopefully you will see ……
This confirms that the Login in working and we can connect to the database from the local machine. We now need to configure and test a network connection. Click Apply and OK to close down the properties dialog.
Also Set your IPALL TCP Port to 1433
And then set your UDL file to connect directly to that port like so.
Notice the IP and port number in the Server name.
This database is now ready for use with DiscoveryQuant 3.0
A new password has been sent to your email.
You have added a user.
This serial number could not be found. Would you like to submit the case anyway?
Your password has been updated.
Your account is now created.
A verification link has been sent to your email.
A new password has been sent to your email.
Your insturment has been removed.
Your privacy settings are now updated.
Software has already been registered to another instrument. Please check your AID and try again.
If you want to change the License Key to another instrument, please submit a new case.
Software has already been registered to the instrument selected.
Please check your instrument's software by going to the Instruments page and selecting the instrument in your "My Instruments" section. Here you will see a Software tab where you can view your instrument's software information.
You can also go to the Registered Software page to view software associated with your instrument(s).
If you are not finding what you are looking for, please submit a new case.