MS SQL Database Usage (optional) |
||
If you have ordered MS SQL databases, ie. separately from mySQL databases, then the ability to administer them is available in your myCP. |
||
If you would like to use a MS SQL database, you must first create it by using your myCP Control Panel. After logging into the MS SQL area, click on "create database". |
||
Database and login name naming scheme |
||
The database naming scheme is automated in myCP. The database name is based on your primary domain name. The first database you setup will be called: abc_com_1. If you request a second DB, it will be called abc_com_2, and so on. Because we use dedicated MS SQL servers, for all clients we need to know the database owners, therefore there can be no exceptions regarding the naming scheme. If you have 2 different accounts, abc.com and def.com, the databases for abc.com must be abc_com_1, abc_com_2, etc, and the databases for def.com must be def_com_1, def_com_2, and so on. The login name will be the same as the database name abc_com_1: The user has full control over the database. It can create, modify and drop tables, add and drop indexes, insert, modify and delete records from a table, etc. |
||
You can now login to the database in myCP my clicking on the Admin link to create your tables, and do all of your MS SQL work. Usually however, you will not need to do this, as this work will be handled by the software you are installing on your site. You may also login to your database with the MS Enterprise Manager (select SQL Server Group, and then Add New SQL Server Registration). The database hostname/server was given to you when you ordered your MS SQL database, for example mssql1.superb.net. You can determine database name by looking at the entry under "database" in the main MS SQL screen in myCP. The database username is the same as the database name. |
||
Each MS SQL database is allocated 20 MB plus 20 MB for its logfile. Additional 10 MB blocks can be purchased for $5 each. |
||
You may want change the password and the user permissions for security reasons. The user created for your database is initially set-up with full permissions for the newly created database. |
||
|
||
Note: if you are not sure why you should change the user permissions, don't do it. You can make your scripts stop working. |
||
Using the MS SQL Admin Suite |
||
|
||