Microsoft KB Archive/260512

= Frequently asked questions - SQL Server 2000 - Tools =

Article ID: 260512

Article Last Modified on 9/13/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Service Pack 3a

-



This article was previously published under Q260512



SUMMARY
This article is meant to address frequently asked questions regarding SQL Server 2000, version 8.0 administration tools.



MORE INFORMATION
 Q: When I attempt to register an OLAP server running on Microsoft Windows 2000 from an OLAP server running on Microsoft Windows NT, I get the following error:

Errors occurred while connecting to.

Cannot connect to the registry on the server computer.

Do you still want to register this server?

How do I resolve this error?

A: To resolve this error, you must start the remote registry service on the Windows 2000 computer by performing the following steps:

 On the Start menu, point to Programs, point to Administrative Tools, and then click Services. Right-click Remote Registry Service and click Start on the shortcut menu.  Q: Can the ON CASCADE DELETE option be set in the GUI interface?

A: Yes. When creating the table in the Diagram UI, click Table and Index Properties. On the Relationships tab, the following two cascading referential integrity options exist:

 Cascade Update Related Fields Cascade Delete Related Records</li></ul>

Select the check box located beside the option you want to implement.</li> Q: When creating a new table in SQL Server Enterprise Manager, I see a field titled Description for each column. How is this field used?

A: The purpose of the Description field is to allow you to store a textual description of each column. (Note there is also a Description field associated with the table.) This description is actually stored as an extended property on the field. When generating a script for the table, there is an option on the formatting page called Include Extended Properties. If this option is selected when the script is generated, the description property will show in the script.</li> Q: Using SQL Server Enterprise Manager, how can I set a database to single user mode and dbo use only mode?

A: In SQL Server 2000, a database cannot be set to both single user mode and dbo use only mode simultaneously. Instead, SQL Server Enterprise Manager allows you to set the following alternative options by right-clicking the database to change, clicking Properties on the shortcut menu, and then clicking the Options tab.

Restrict access

<ul> When this option is not selected, normal operating state access to the database is allowed.

</li> When this option is selected, the following settings are available:

<ul> Members of db_owner, dbcreator, or sysadmin

When selected, this option restricts access to the database only to members of the db_owner, dbcreator, or sysadmin roles.

</li> Single user

When selected, this option restricts access to the database to only one user at a time.

</li></ul> </li></ul>

Note that both of these options still exist for SQL Server 6.5 and 7.0 databases. However, if you are using SQL Server 2000 tools, you can no longer set these options on the database properties tab in SQL Server Enterprise Manager. Instead, these options can only be set on SQL Server 6.5 and 7.0 databases by running the sp_dboption stored procedure.</li> Q: Can I have both SQL Server 7.0 and SQL Server 2000 client management tools installed on the same computer?

A: No. During an installation upgrade, the SQL Server 7.0 tools are replaced by the SQL Server 2000 tools. Additionally, when installing SQL Server 2000 as a separate instance, if you choose to upgrade the tools, the SQL Server 7.0 program group remains and the SQL Server 2000 program group is added. However, the icons in the SQL Server 7.0 program group actually execute the SQL Server 2000 tools instead of the original SQL Server 7.0 tools.</li> Q: Is it possible to define a special template that is automatically copied into the query pane for Query Analyzer when you select New?

A: Yes. By default, a blank document is always displayed. However, you can define and save a special template by typing the Transact-SQL statements into a window in Query Analyzer, choosing Save As, and saving it in the directory you want as a Template SQL File (*.tql). Then, by selecting the drop down New icon on the toolbar and choosing Template, you can select the template you want to open.</li> Q: Is it possible to use SQL Server 7.0 tools to connect to SQL Server 2000?

A: It is recommended that you upgrade your tools to SQL Server 2000 if you plan to connect to a SQL Server 2000 server, due to the fact that most SQL Server 7.0 tools will not connect to SQL Server 2000 servers. The only SQL Server 7.0 tools that can connect to SQL Server 2000 servers are Query Analyzer and OSQL, but neither of these tools can be used to connect to named instances of SQL Server 2000 servers.

</li> Q: Is it possible to use SQL Server 2000 tools to connect to SQL Server 7.0?

A: Yes, all SQL Server 2000 tools are backward compatible with SQL Server 7.0.</li></ol>

Didn't see an answer to your question? Visit the Microsoft SQL Server Newsgroups at: Microsoft SQL Server Newsgroups

Comments about this or other Microsoft SQL Server Knowledge Base articles? Drop us a note at [mailto:sqlkb@microsoft.com SQLKB@Microsoft.com]

Additional query words: faq referential integrity ent man entman SEM SSEM

Keywords: kbfaq kbinfo KB260512

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.