ARE YOUR SQL SERVER 7.0 LINKED SERVERS SECURE?

SQL Server 7.0 doesn't allow multiple hops between servers. As a result,
impersonation for NT authentication is also not allowed. To work around
this problem, if you have ServerB as a linked server on ServerA, use SQL
Server standard logins as remote logins. If the public role has
permissions to more database objects than is necessary, remove the permissions
from the public role and grant them to another system- or user-defined
database role. If the permissions needed by the linked server are a small
subset of database objects, grant permissions for the small subset of
database objects to a new user-defined database role. If the permissions needed
by the linked server are for the majority of the database objects, use a
system-defined role. For example, ServerA has ServerB as a linked server
and has defined the remote user as ServerB_user. ServerB has a new
user-defined database role, ServerA_db_role.

The following are necessary for the server's linked server setup for
ServerA:


* ServerB is the linked server.

* ServerB_user is the linked server remote SQL Server standard login.

* ServerB_db_role is the user-defined database role.

* ServerB_user is a member of ServerB_db_role.

* Permissions needed only by ServerB are granted to ServerB_db_role.


VISUAL STUDIO.NET DEBUTS

Microsoft's launch of Visual Studio.NET (VS.NET) marks the beginning of
.NET, the company's initiative to incorporate XML-enabled software and
Web services. To learn more about this much-hyped technology from a
development standpoint, read Tech Update's special report.
http://clickthru.online.com/Click?q=a1-AfVtQ-ZMdojKdFeGklI9XlDGs39R 

----------------------------------------