Re: Permissions on master..sysservers

From: Mateo (m_leija_at_hotmail.com)
Date: 10/07/03 

Date: Tue, 7 Oct 2003 10:17:01 -0600

The application does perform a 'select *' and would require a rewrite. The
application uses linked servers to link to other SQL Servers. The
providerstring column is null for the linked servers, so it may be OK to
remove the constraint.

I've noticed the constraint is across all of our SQL2K SP3 installations,
but not SQL7. Granting the account 'System Administrators' permissions gives
it the necessary permissions to perform the select, but this is not an
option.

Thanks for your help,
Mateo

"Jasper Smith" <jasper_smith9@hotmail.com> wrote in message
news:uKdsFDKjDHA.1784@tk2msftngp13.phx.gbl...
> Off the top of my head I would guess this is because that column could
> contain a user/password combo in the provider string. Does the application
> require that column (is it doing a select * ?) , would it be possible to
> rewrite to not access that column if it was not required ? The danger
would
> be exposing a user/password I guess but if you have no linked servers set
up
> exposing that information then it may not do too much harm to allow select
> against it.
>
> --
> HTH
>
> Jasper Smith (SQL Server MVP)
>
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Mateo" <m_leija@hotmail.com> wrote in message
> news:%23is%23m8FjDHA.1544@tk2msftngp13.phx.gbl...
>
> We have a vendor application that performs a select statement on the
> master...sysservers table (SQL2K). However, there's a 'Column Deny' select
> constraint on the providerstring column causing the select statement to
> fail. Is this standard or is there a SP or Hot Fix that made this change?
> I'd like to know the risks of removing this constraint.
>
> Thanks in advance,
> Mateo
>
>
>

Relevant Pages

  • Re: Permissions on master..sysservers
    ... Jasper Smith (SQL Server MVP) ... I've noticed the constraint is across all of our SQL2K SP3 installations, ... > constraint on the providerstring column causing the select statement to ...
    (microsoft.public.sqlserver.security)
  • Re: Copying from one record set to another
    ... I had a version using linked servers in SQL Server, ... I have another thread in the SQL server newsgroup looking for an answer ... read about linked tables in Access online help - a linked table can be ...
    (microsoft.public.data.ado)
  • Re: How to use ODBC datasources in SQL Server 2005 x64
    ... I migrated from SQL Server 2000 Standard to SQL Server 2005 Standard x64. ... Now i try to get the linked Servers working, ... The MSDASQL (ole db provider for ODBC data sources) is missing. ... SQL Server 2005 x64 does not support ODBC Data sources as linked servers!! ...
    (microsoft.public.sqlserver.connect)
  • Re: temp db indexing in SQL2k
    ... SQL Server has something called deferred name resolution. ... But if all tables in a query exists, then all other objects in the ... Maybe your scenario with linked servers changes the scene here, ... Books Online for SQL Server SP3 at ...
    (microsoft.public.sqlserver.programming)
  • How to use ODBC datasources in SQL Server 2005 x64
    ... I migrated from SQL Server 2000 Standard to SQL Server 2005 Standard x64. ... Now i try to get the linked Servers working, ... The MSDASQL (ole db provider for ODBC data sources) is missing. ...
    (microsoft.public.sqlserver.connect)