Point and click queries.

            Any data source.

                        Any computer.

                                    Data server.

                                                Free.


          Microsoft SQL Server
                ( Please scroll down. )

Disclaimer

Brand names are addressed only as a service to CoreReader users. See the source specifics page for details.

To add to these notes or to add your favorite data source, see instructions on the source specifics page.

Source

The CoreReader test environment includes a Microsoft Enterprise Server version 7 on a Ms. Win2k Server, a Ms. Enterprise Server version 7 running on NT 4.0 SP6, and a Ms. Server version 7 running on Win2k Workstation.

Running With Microsoft SQL Server

Sometime prior to release number 20921, Microsoft made a hidden change in their data sources. Whether it was part of their recent frenzied security repairs or more of their infamous attempts to control us cannot be known. What is known is that any CoreReader releases before that date will not function with current Ms. data sources.

It pains me to say anything good about that company, but data connections to their databases are the best, simply because they are simple and straight forward ( relatively speaking ).

Database Abstraction

If the appender is used in Sql Server, the inclusion of the dbo is required. ( Which I tend to forget, and which almost caused me to drop the feature from CoreReader because I thought that it had stopped working. ) Refer to the Database Abstraction section of the documentation for details.

Connection Strings

Remember that, if it is necessary, CoreReader will accept parameters along with a connection string. This allows the simplicity of entering parameters with enhancement by the connection string. When using both, do not duplicate values.

Exclude the carriage returns in the following examples which are used here for readability. Also, except in a driver name, spaces are also usually taboo.

Security

A Ms. SQL Server connection can use either the server's security or windows security. CoreReader always tries to use the server's security. That may not work if your organization supports only windows security.

Microsoft recently began pushing windows security for logins instead of using the server's security. If your organization requires that you use windows security, then use a connection string so you can use non-standard parameters in the connection. In the connection string, include the Trusted_Connection parameter.

An ODBC connection string using windows security might be something like:
Driver={SQL Server};
Server=Server1;
Database=northwind;
Trusted_Connection=yes;

The very same connection string using server security might be something like:
Driver={SQL Server};
Server=Server1;
Database=northwind;
UID=myLoginId;
Pwd=myPassword;

If using a DSN with windows security, the string might be something like:
"DSN=dataSourceName;
Trusted_Connection=yes;

Using OLEDB

OLEDB connections are more confusing, slower, and used less often.

An OLEDB connection to a Ms. SQL Server 2000 can use either the SQLOLEDB or the MSDASQL data socket. Although newer, SQLOLEDB does not allow multiple connections and does not maintain a connection as well as the older MSDASQL.

This web site is maintained with Notepad.

Copyright 2001 - 2010 John Ragan.