Do I need to reapply SP1 after adding new components?

Hello,

I applied SQL 2005 SP1 and hotfixes to my instance. Now I found the SQL_replication component was not installed. I just installed that component.

1. Do I need to reapply SP1? Then hotfixes?

2. Will reapply SP1 or hotfixes cause problems? I tried on my test server, the SP1 install failed with some errors the first time. It went through Ok the second time. (I have 3 instances on this test server. I only added new component to one instance. When applying SP1 the second time, the installer forces me to apply on all instances and tools; causing outage to all instances. The installer did not force me when I applied SP1 the first time.)

I wonder what is the best practice for handling this case.

thanks,

ktmd

Yes, you will have to.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Do I need to install SQL Server to second node in cluster prior to adding the node?

I read these instructions:

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

But I'm not sure if I have to install SQL Server first on node 2, then add it to the cluster. Or does adding it to the cluster also install the software?

Thanks

From your question, I assume that you have an functioning single node cluster.

Add Node2 to the Windows MSCS cluster, and then install SQL Server on Node2. SQL Server will locate the cluster and ask if you are adding this Node to the SQL Server Virtual Server.

Distributing/importing semantic models

Hi,
i'm using SQL Server 2005 Reporting Services to create ad-hoc reports.
Using the BI Dev Studio i'm defining a DSV and adding queries to it
before refining in the semantic model. i need to be able to distribute
these to our customers, who use an SS DB with known schema.
In a simulated customer environment i've successfully imported the DSV
file (using SMSS) to RS. When i subsequently try to import the SMDL
file i get an error complaining that the DataSourceView element is
missing from the SemanticModel. Quite correct. But how do i specify
the DSV element or otherwise make the association?
It is quite acceptable to me to make a simple text edit to the SMDL
file.
TIA for any help.OK, slight correction - i haven't successfully imported the DSV.
Import appeared to succeed but there's actually no data visible for it
in SMSS.|||Since there are no replies i'm either very stupid or nobody knows. If
it's the latter then for the benefit of all here's how i did it in the
end.
DataSourceView is a valid element of the SemanticModel element. So
manually edit your SMDL file and paste the entire content of your DSV
file (which is a single DataSourceView element) just above the
SemanticModel closure tag ("</SemanticModel>").
The Management Studio will now happily import the modified SMDL file.
The customer just needs to manually change the Data Source to their own
database using Management Studio (or Report Manager).
Cheers all.