Common answers to queries relating to Shared SQL Services, Dedicated and VPower SQL Servers and other Database issues can be found on this FAQ:
When we set up your account you'll receive an e-mail containing your login details, which includes the Server Name, Username/Password and Database configured for you. You'll receive two sets of Username/Password (see below for more information on this). We configure all logins and databases for British English, using all other default settings. Your database will be configured to grow at a rate of 10% up to the maximum allowed with your Service Plan.
We configure 2 sets of logins for different purposes. This is to help protect your Database against abuse and prevent unauthorised tampering. Your first login is known as the "SQLAdmin" Login, and is to be used when working with SQL Enterprise Manager or Management Studio, and gives you DBO rights to administer your database as you need to. The second login, "WebUser" is designed to use within your Web Pages to call the SQL Server from within your ASP/ASP.NET Code. This login has the ability to read and write records (known as "datareader" and "datawriter"), but cannot alter the structure etc and has no special rights. You MUST use this login when calling pages on your Web Site to aid with security. We may suspend your account if we believe the wrong logins are being used and threatening the overall security of our services.
We create Databases using a numbering scheme to ensure that there are no conflicts between you and other customers, and do not allow customers to choose a database name. Please note that some legacy accounts created before July 2008 may use an older naming convention. This also helps protect your privacy as the individual databases are not immediately identifiable.
In general, your login can do almost any task that a DBO would typically undertake, such as:
- Create new objects within the database (tables, views, stored procedures etc)
- Delete objects from your database
- Change the ownership of database objects
- Manually initiate backups of your database when required (see below)
- Take your database offline
- Grant permissions to your database to any other existing username on the server (use with caution!)
(this list is not exhaustive)
You cannot:
- Make any server/global changes, such as creating additional databases.
- Create new users on the server (although our HelpDesk Team are happy to help with this where necessary)
- Restore backups of your database (our HelpDesk Team can help you with this where required)
- Bring your database online after it has previously been taken offline
If you encounter issues making a change you believe you should be able to make, contact our Support Team who can help you make the relevant changes where it is not likely to cause other issues with the Shared SQL Platform.
Contact our HelpDesk in the usual way, ensuring you quote your database name and what you want us to do (and which backup you want to restore) and we'll assist you. Please note that your database will generally be taken offline and therefore your service interrupted. Any modified data will be lost when we restore your database.
While SQL Server's default port is 1433, our servers run on alternative ports. The port number will vary depending on a number of factors, and you are advised to refer to your original login details. When you quote the server in your web site code, you would typically use "my-server-name,port" (where port is the number your SQL Server is configured with). When using Enterprise Manager or Management Studio, the port can be specified either manually in the appropriate option on-screen or by quoting the "my-server-name,port" format again.
We strongly recommend you put them in one of the special locations rather than within a standard ASP or ASP.NET File. Our general recommendation is to place in your global.asa file for Classic ASP, and in web.config for ASP.NET. This will help reduce the chance of your SQL Database being compromised through code exposure methods.
This is often because you have not specified the port number correctly (see above), or are not connecting from the Static IP Address which your account is configured to allow (where applicable). Also, if you are getting login errors, check your username/password carefully - the passwords are long for security purposes and it is easy to make a mistake.
Run bespoke business applications on VPower Servers without needing to buy and run expensive hardware.
Find out more