The online FAQ database contains hundreds of answers to frequently asked questions, articles on using our
web server applications and other related technologies, and resolutions to common problems. If you are seeing
an error message, be sure to try searching on the error message or error number that you are seeing.
|
| |
| |
| |
| |
|
I want to use your auction and classified software, but want to use it with a different type of SQL database than what you support. I am an experienced developer. Do you think I can do that?
|
|
|
Currently, all XCENT web server applications support Microsoft SQL Server databases for all larger scale sites or when the performance, stability and security matter most. Entry level sites may use a Microsoft Jet database (MDB file on the web server), but that doesn’t apply in this article. In our opinion, any developer that is experienced in modern databases and has real experience with ASP VBscript and the various SQL dialects will certainly be able to adopt the software for use on a different backend database server.
The important points we will point out is that the new target database must be able to support a few key type of technologies or techniques in order to make this type of implementation as easy as possible for the developer. Most of these are widely supported by many of today’s modern SQL database platforms. These would be (note some are “must” requirements and some are “should” requirements):
- The target database must fully support connectivity via a supported ODBC or OLEDB driver that can be used in the ASP application via Microsoft ADO.
- The target database must be able to support default value constraints on specific fields/columns in the tables.
- The target database must be able to support NULL values for string and numeric fields.
- The target database must be able to support an integer based unique record identity value that is automatically generated by the database on new record inserts. In Microsoft SQL Server, this is known as an IDENTITY column (unique key).
- The target database must be able to support MIN, MAX, and COUNT aggregate functions. The MIN aggregate function returns the lowest value of the specified column in an aggregate group of records. The MAX aggregate function returns the highest value of the specified column in an aggregate group of records. The COUNT aggregate function returns the number of records in an aggregate group of records.
- For performance, the target database should support multiple indexes per table.
- For performance, the target database should support the concept of a clustered index. This is where the physical order of the rows in the table is the same as the logical or indexed order of the values in the index key. Due to the fact that the rows are actually stored in the database in the physical order that the index enforces, only one clustered index per table can be created.
- The target database must be able to support sub-queries.
- The target database must be able to support stored procedures.
- The target database must be able to support recursively called stored procedures (for v4.x or later applications). The number of recursion levels deep the database must support will vary based on specific installations of the software. However, at least a dozen levels deep of recursive stored procedure calls should be a minimum for most real-world installations.
|
|
|
|
| |
