.. ==================================================
.. FOR YOUR INFORMATION
.. --------------------------------------------------
.. -*- coding: utf-8 -*- with BOM.

.. include:: ../../../Includes.txt

MsSQL
^^^^^

bAnsiOff
--------

Some MsSQL databases require the client to have specific ANSI settings (you'll notice as you'll get an error). In this case the client needs to tell the server to allow ANSI null values and thus set ANSI to be off. If you have this enabled default: not enabled) the SQL Frontend will initially run the following two commands: ::

    SET ANSI_NULLS ON
    SET ANSI_WARNINGS ON

bLimitManually
--------------

Boolean and only for very special occasions. As you might or might not know, the SQL Frontend works with limitations in the SQL statements which means for MsSQL servers the use of the keyword **TOP**. Anyhow, on some servers, this slows the statement actually down than (intentionally) up. Thus, if you encounter veeery slow processing you could try setting this setting to true in order to avoid this keyword (and, alternatively, select everything but limit by using PHP).

sTimestampOnAdd
---------------

If set and not empty, everytime a new entry is created the current unix timestamp is written to this field.
Quite common in TYPO3 table is the column name **crdate**, altough it's, of course, not obligatory.

sTimestampOnEdit
----------------

Basically the same as sTimestampOnAdd but for editing. So everytime an entry is updated, the current unix timestamp is written to this field. Common in TYPO3: **tstamp**

sTimestampOnDelete
------------------

Basically the same as sTimestampOnAdd but for deletion and thus only useful if bSetDeleteFieldInsteadOfDeletion is set. Not common in TYPO3 (or, if so, used within **tstamp**).

Deletion and marking deleted
----------------------------

If you delete something from a database table, it is deleted. Removed. Gone. *Unless* you don't really delete it but instead mark it being deleted. This is, what a lot of applications (within TYPO3) do in order to be e.g. capable of providing a recycler. Entries are only marked deleted when users delete them and thus not shown anymore, but in the database they still persist and can be restored.

For this to be achieved in a SQL Frontend, you may use the following settings telling the system which column is the one to carry the marks and what values it expects for both, entries that are deleted (sDeletedTrue) and entries that aren't (sDeletedFalse).

=================================  ===========  ===========================  =======
Configuration name                 Value type   Description
=================================  ===========  ===========================  =======
bSetDeleteFieldInsteadOfDeletion   boolean      true to enable this feature  false
sDeleteField                       string       column name                  deleted
sDeletedTrue                       string       value for deleted entries    1
sDeletedFalse                      string       value for "alive" entries    0
=================================  ===========  ===========================  =======

Default values (except bSetDeleteFieldInsteadOfDeletion) represent default TYPO3 configuration. Thus, if you are displaying any TYPO3 table and want to use this feature, most likely you just need to set bSetDeleteFieldInsteadOfDeletion to true.