2014.10.26 MSS Code Factory 1.11.12514 SQL Server sp_create() establishes chain links

If you have no chains defined in your model, I highly recommend downloading this release
and remanufacturing your entire project.  In fact, it's got such important changes for
SQL Server that I'm going to make it the default download for MSS Code Factory instead
of SP4.  Just don't try to model chains yet.

SQL Server now establishes prev/next links for chains.  I've also modified the SQL Server JDBC
to properly report errors thrown by the database engine, so it now passes the delete permission
check tests.

What's odd is that instead of throwing an exception about an integrity constraint, SQL Server
instead seems to continue on with processing after the delete fails, and then gets an error
because a cursor is still in existence when the next iteration of the delete-by-index loop
tries to remove an instance.  I'm not sure how to address that problem -- I kind of count
on a stored procedure throwing an exception and stopping execution when an exception is
raised.  Maybe I need to modify the stored procedures to explicitly check to see that an
instance has been deleted (by analyzing the SQL status variable), and manually raise an
exception to get the processing to stop.  I'm not going to worry about it right now -- I'll
deal with such changes when I'm doing the modifications to the delete processing for breaking
the chain links.

The CFSecurity 2.0 model has been updated to reduce certain string columns to 192 characters
so that they can be properly indexed by MySQL.  I didn't like the idea of the most fundamental
of the models causing errors during the installation of any of the databases.  So you're now
restricted to 192 character names for email addresses (user id strings), cluster addresses,
tenant names, and JEE mount points.