As Steve mentions we're starting work on the next release of SQL Server, although it's not code named Nirvana. Several SQL blogs divulge the code name so I won't include...

Hi Steve,

I agree that some companies need a kick in the pants to get security fixes out. The hammer of full public disclosure of the threat could be that kick. Or...

Hi Steve,

I have to agree with you (not that it hurts or anything) about the security point - falling in the middle between immediate disclosure and no disclosure. However, a...

Check out: http://msdn2.microsoft.com/en-us/library/ms143688(SQL.90).aspx

Basically on the Feature Selection dialog, the one with the feature tree, you can select a node on the tree and the Browse button at...

That's very very strange. While I'd expect the tools directory to exist I wouldn't have expected setup to block based on the existence of the tools directory. It's great if...

Okay - From Node 2 try removing the complete "Workstation Components" feature through Add/Remove programs. Then rerun setup from the DVD and choose to install only tools.

SQL2K can be a default or named instance. The only restriction is that instance names must be unique - you can't have a SQL2K and a SQL2K5 instance with the...

Compatibility mode is only about versions (7.0, 8.0, 9.0) and not editions (Workgroup, Standard, Enterprise). There is no way that I know of to run Enterprise Edition with Standard Edition-only features.

Randy, You can installed a SQL2K5 Cluster side-by-side with a SQL2K cluster. This is a supported scenario. When you're ready to upgrade you'll need to use the copy database wizard,...

In SQL2K the tools were installed on all nodes that were part of the SQL cluster. However, in SQL2K5 that behavior was changed and the tools (this should read non-instance...

From your description it sounds like your viewing the list of tables in the "Summary" view in Management Studio. This view displays Name, Schema, and Created. Where Created displays as...

By default in a cluster install the tools are only installed on the primary node (the node that setup was original run). From what you describe, though, it sounds like...

Hi Alpesh,

The supported upgrade paths are documented here: http://msdn2.microsoft.com/en-us/library/ms143393(SQL.90).aspx.

In short, SQL2K Ent can only be upgraded to SQL2K5 Ent. However, this is a in place setup-based upgrade....

Take a look at the Books Online topic: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/45154b65-b46f-4aad-82e4-261376a7e9d4.htm

You can access this online at: http://msdn2.microsoft.com/en-us/library/ms143241(SQL.90).aspx

Cheers,

Dan

SMO is compatible with SQL Server version 7.0, SQL Server 2000, and SQL Server 2005.

Cheers,

Dan