Can I increase the size of my database/device? How about decrease?
You can increase the size of your database and/or your device by purchasing additional disk space.

You cannot decrease the size of your database or device.

How many databases/devices can I have? Is there a setup fee?
You can purchase unlimited databases in a shared device or move to a higher plan that allocates a dedicated device. Each plan is accompanied by a non-refundable setup fee for the first purchase. Once you are enrolled in a plan, there are no subsequent setup fees when purchasing additional features (logins, disk space or databases).

How many SQL logins do I get? Can I get more?
With each database, you are allocated up to a certain number of logins. Additional logins can be purchased in blocks of five (5). Logins cannot be transferred between databases residing in a shared device (plan 1 & 2). If you have a dedicated device (plan 3) logins are allocated to the device and can be used by any database within that device.

Why can’t I choose the name of my devices, logins or databases?
Security is priority #1. Our SQL servers are shared among multiple users and accessible over the internet. In addition to employing the most comprehensive security measures in the industry, the device, login and database naming scheme has been designed to preserve the customer’s anonymity as an additional layer of security.

What do I get with each plan by default?
Depending on the plan, you get a certain amount of database storage or a dedicated device with a certain amount of storage and a certain amount of databases. Regardless of the plan, you get the following standard features:

• The first login for each database, is dbo-aliased (database owner). Additional logins can be dbo-aliased at no extra charge. Guest access is available upon request.
• Every database is accompanied by a separate transaction log residing in a separate shared device (plan 1 & 2) or a separate dedicated device (plan 3).
• Daily (transaction logs) and weekly (database) backups are performed.

Who is responsible for database administration such as permissions?
You are. Each database has a login which is dbo-aliased. By using SQL Enterprise Manager or Transact-SQL and this login, you have full control of your database(s), including the creation of groups, permission allocation, object creation etc. Any option changes not available to the dbo must be submitted to tech support.

What about transaction logs and backups?
In order to accommodate robust SQL applications, transaction logs are never kept in the same device as your database. Instead a separate device is created, dedicated to the transaction logs. Depending on the plan, this device is either shared or dedicated. By default, the transaction log size is ½ of the database size. Every database is being backed up on a daily basis (transaction logs) and weekly (database). On-line back up is utilized so there’s no down time. There’s no additional charge for the transaction log disk space or the daily/weekly backups. There is, however, a restore fee associated with every SQL restore request.

When does the backup rotation begin?
Once your database is created, it will enter the backup rotation on the very next weekend when a full backup will be performed.

Do I need to purchase SQL Client Access Licenses?
No. Your databases can only be accessed via TCP/IP sockets over the internet. Worldwide Internet’s systems are already fully licensed for SQL access over the internet.

How can I access my SQL server?
Worldwide Internet’s SQL servers are designed and licensed for access over the Internet using TCP/IP sockets. Each server has both a host name and an IP address. You can use either to address the server.

What do I need to do on my client side (ODBC and ODBC-less)?
You must define SQL Server advanced network entries with the Client Configuration Utility, which is necessary to exist on your client in order to enable TCP/IP sockets access via the internet. Please consult the following Microsoft document for more details:
http://support.microsoft.com/support/kb/articles/q137/6/35.asp

What programs/utilities can I use to access my SQL server?
You can use SQL utilities such as:

• SQL Enterprise Manager
• ISQL_w
• SQL Server Web Assistant
• MS Query

Additionally, you can access our SQL servers via any application that supports native SQL or ODBC connectivity using TCP/IP over the Internet. Some examples are:

• Borland Database Engine (Borland Delphi, C++ Builder, JBuilder etc.)
• Microsoft Visual Studio (Visual Basic, Visual C++, Visual Interdev etc.)
• Microsoft Active Server Pages (ASP)
• Allaire Cold Fusion

Please note that your client computer must be properly configured for SQL access using the TCP/IP sockets net library. Look at the previous answer for more information.

What version of SQL are you using?
All servers are running MS SQL 6.5 with SP4.

What Net Library do I use in my SQL Client Configuration Utility? What kind of security mode?
TCP/IP Sockets, Standard Security.

What Character Set does the SQL server use?
ISO 8859-1

What Sort Order does the SQL server use?
Dictionary Order, Case Insensitive.

Can I use the transfer utility to transfer data to my WIPC SQL server?
Yes. You can use the transfer under the following scenario only: You must make your source database temporarily available over the internet so we can perform a pull transfer from your source server to the WIPC destination SQL server. Push transfer from your server to the WIPC SQL destination server is not supported for security purposes.

What can I do if I have a large database that I cannot transfer?
After we allocate a database name for you, you may put your entire database on a CD and send it to us so we can manually mount it on the SQL server. This feature is free for Option 3 customers. There’s a one time fee of $100.00 for Option 1 and 2 customers.

Do you support SQL replication?
Yes. Our SQL servers can act as "Subscription Servers" but not as "Publishing Servers" or "Distribution Servers". Additionally, if your publishing server is MS SQL 6.5 you can also publish to an ODBC DSN pointing to our SQL servers.