Question

  Asked: Apr 10 2008   6:43 AM GMT
  Asked by: WarwickW

Potential over & under security issues with SQLNative Client ?

Hello,

I've been unable to find any reports of these two problem when using the SQL Native Client driver

(9.00.3042.00), so I'm hoping else has seen these.

Firstly check constraint definitions accessed by the following TSQL only returns data with the SQL Server

driver, ie nothing with SQL Native Client. Permissions are the same, just the driver in the (file) DSN

changed.

TSQL is:
Select sys.check_constraints.Name, Definition from sys.check_constraints inner join sysobjects on

sys.check_constraints.parent_object_id = sysobjects.id where sysobjects.name = 'MYTABLE' and

sys.check_constraints.type = 'C'

Secondly, When using SQLNCL instead of the SQL Server driver we are finding that ado(2.8) recordsets are

returning more fields than the view has Select Statement. It turns out that these fields are inputs to the

view, and potentially not for external viewing.

Eg if we have:
Table1 with Columns T1A, T1B, T1C and;
Table2 with Columns T2A, T2B, T2C and create a view
"Select T1A, T2A from Table1 inner join Table2 on .....etc.. "

we can also see the other columns in the ado recordset when accessing this view via ado and SQL Native Client!

Any help much apprecated.

We want to move to SQL Native Client to allow better connectivity to a 64bit SQL Server

Thanks,

Warwick