Microsoft SQL Server 2005 disappears on one node.

Hi,
Our production database set on cluster SQL Server 2005 (SP1). I installed
client tools for all 4 nodes. Every node should show Microsoft SQL Server
2005 and Microsoft Visual Studio 2005 after click All Programs, but in one
node the Microsoft SQL Server 2005 disappeared.
While I go to Add or Remove Programs, I saw following items:
Microsoft SQL Server 2005 (64 bit)
Microsoft SQL Server Backward compatibility
Microsoft SQL Server Books online (English)
Microsoft SQL Server Native Client
Microsoft SQL Server Setup Support Files (English)
Microsoft SQL Server VSS Writer
It seems like nobody removed the client tools, but why it doesn’t show? How
to restore it to Start -> All Programs -> Microsoft SQL Server 2005?
Regards,
Chen
The client tools were never installed on that node. The installer for the
tools is not cluster-aware. Each node's client tools must be installed
separately from the local machine.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:26B7492E-F768-425D-8DD3-6A91512C584D@.microsoft.com...
> Hi,
> Our production database set on cluster SQL Server 2005 (SP1). I installed
> client tools for all 4 nodes. Every node should show Microsoft SQL Server
> 2005 and Microsoft Visual Studio 2005 after click All Programs, but in one
> node the Microsoft SQL Server 2005 disappeared.
> While I go to Add or Remove Programs, I saw following items:
> Microsoft SQL Server 2005 (64 bit)
> Microsoft SQL Server Backward compatibility
> Microsoft SQL Server Books online (English)
> Microsoft SQL Server Native Client
> Microsoft SQL Server Setup Support Files (English)
> Microsoft SQL Server VSS Writer
> It seems like nobody removed the client tools, but why it doesn’t show?
> How
> to restore it to Start -> All Programs -> Microsoft SQL Server 2005?
> Regards,
> Chen
>
|||Hi Geoff,
Thanks for reply.
The client tools were installed on every node and I applied SP1 on every
node before database migrates from SQL Server 2000 to this cluster server. It
could be someone removed? What I need to do get this back, just re-install
the client tools on this node?
Regards,
Chen
"Geoff N. Hiten" wrote:

> The client tools were never installed on that node. The installer for the
> tools is not cluster-aware. Each node's client tools must be installed
> separately from the local machine.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Chen" <Chen@.discussions.microsoft.com> wrote in message
> news:26B7492E-F768-425D-8DD3-6A91512C584D@.microsoft.com...
>
|||Yes. A simple reinstall should correct the issue.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:65616AD1-8DB6-44C3-B334-82797375FCE1@.microsoft.com...[vbcol=seagreen]
> Hi Geoff,
> Thanks for reply.
> The client tools were installed on every node and I applied SP1 on every
> node before database migrates from SQL Server 2000 to this cluster server.
> It
> could be someone removed? What I need to do get this back, just re-install
> the client tools on this node?
> Regards,
> Chen
> "Geoff N. Hiten" wrote:

Mgmt Studio: Script Table as...

Hi,

I'm using SQL Server 2005 Express SP1 & Mgmt Studio express.

I'm trying to use the script output to track my db changes in source code mgmt, but when I output a table to a script the first two bytes of the "text" file are 0xFF and 0xFE which sends my SCM into storingthe file in binary defeating the purpose of storing text files I can "diff" to see the changes.

Does anyone know why the mgmt studio is doing this and is there a way to stop it?

thanks!

Management Studio creates UNICODE files so characters from all alphabets can be represented in the same file. Your SCM system is probably interpretting the UNICODE signature at the top of the file as being "binary."

If you are scripting to a Query Editor Window, you can save the script as an ASCII file by clicking File | Save As... and clicking the little pull-down arrow on the right side of the save button to select the file type. US-ASCII is toward the bottom of the list.

Hope this helps,
Steve

|||

Thanks! This was helpful and it explains the situation.

I'm working around it by the copy & paste method you mention while I deal with the SCM issue.

It's interesting that SQL Server Mgmt Studio uses unicode BOM and Visual Studio uses utf-8 for it's configuration files, so the SCM has to deal with the many "standards" of unicode...

life was not mean't to be easy...

Metadata cleanup has deleted metadata at the Subscriber incorrectly?

Hi,

We have Microsoft SQL Server 2005 SP1 based merge replication application. This system consist of 1 publisher/distributor and about 700 subscribers. Publisher is MS SQL Server 2005 standard SP1 and subscribers are mostly MS SQL Server Express SP1s.

We started this system in September last year with migrating data as region based with one area at time. Everything went well until January 2007 when over 500 users were using new system. What is even strange that most errors comes on areas which were moved to new system on week number 2 on 2007 (8.1.2007->)

I have double and cross checked that these publications have exact the same parameteters as working publications.

The error message which comes on subscriber is following:

The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Subscriber for changes not yet sent to the Publisher. You must reinitialize the subscription (without upload). (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199401) Get help: http://help/MSSQL_REPL-2147199401

When this error comes client subscription should not be expired yet. So subscription is expiring incorrectly earlier than expected. After reinit subcriber can syncronize without any errors. For now machines suffering of this error have been different machines so there is no certain information if this error is repeatable on same machine.

Real bad thing is that if user has't syncronized in regular basis there is possibility to that data may be lost because the reinit must be done without upload as error message says.

Regards,

Jouko

We have now installed SP2 to over 650 machines and we are still getting this error. So it seems obvious that SP2 do NOT fix this error. We have now open second time support case to Microsoft about this issue. First time we got answer to apply SP2 to all machines that are involved with replication.

Jouko