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.

Do I need second license?

Hello,
I have MS SQL Server 2005 Standard Edition with one Client Access License.
May I
install the server as Primary on one machine and as Secondary (backup)
with Log Shipping on it on another machine, using same license?
Thanks,
GBYes,
But, note, its there for backup only and should not be used to run queries
etc...
So, if you ship the logs across to the backup server and then use database
snapshots then you are probably breaking the liecence terms and need another
liecence.
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"GB" <gennady@.telus.net> wrote in message
news:79SJf.7479$n67.3175@.edtnps89...
> Hello,
> I have MS SQL Server 2005 Standard Edition with one Client Access License.
> May I
> install the server as Primary on one machine and as Secondary (backup)
> with Log Shipping on it on another machine, using same license?
> Thanks,
> GB
>|||Since GB really asked two questions (one in the subject and one in the body)
in which a YES can answer both but it has opposite meaning I wanted to say:
No you don't need two licenses<g>.
Andrew J. Kelly SQL MVP
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:O0phfIUNGHA.2472@.TK2MSFTNGP11.phx.gbl...
> Yes,
> But, note, its there for backup only and should not be used to run queries
> etc...
> So, if you ship the logs across to the backup server and then use database
> snapshots then you are probably breaking the liecence terms and need
> another liecence.
> Tony.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlserverfaq.com - free video tutorials
>
> "GB" <gennady@.telus.net> wrote in message
> news:79SJf.7479$n67.3175@.edtnps89...
>|||Lol - teach me for reading the Q and ignoring the subject - doh!
Absolutely Andrew, and thanks for waking me up!
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:e7XMoyVNGHA.536@.TK2MSFTNGP09.phx.gbl...
> Since GB really asked two questions (one in the subject and one in the
> body) in which a YES can answer both but it has opposite meaning I wanted
> to say: No you don't need two licenses<g>.
> --
> Andrew J. Kelly SQL MVP
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:O0phfIUNGHA.2472@.TK2MSFTNGP11.phx.gbl...
>

Distribution DB constantly grows

Hi,
I have set up transactional replication for a database from one db
server to a second. The replication is working fine but the distribution
database constantly grows. The size of the replicated db is 524 MB, the
size of the distribution db is 24 GB, growing daily.
How can I shrink my distribution database and how can I limit the growth
without damaging the replication?
Markus
you need to maintain the tlog on the distribution database. Make sure it
using the full recovery and dump the tlog every 5 minutes or so. You might
want to backup the log with truncate_only, shrink the tlog, and then backup
the database.
Then check your transaction retention period, it should be 48 hours. Make
sure your distribution clean up job is enabled and running every 10 minutes.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Markus Renschler" <SP-news@.renschler.net> wrote in message
news:%23uv0qzXdFHA.2420@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have set up transactional replication for a database from one db server
> to a second. The replication is working fine but the distribution database
> constantly grows. The size of the replicated db is 524 MB, the size of the
> distribution db is 24 GB, growing daily.
> How can I shrink my distribution database and how can I limit the growth
> without damaging the replication?
> Markus
|||Hi Hilary,
thanks for the advice.

> you need to maintain the tlog on the distribution database. Make sure it
> using the full recovery and dump the tlog every 5 minutes or so. You might
> want to backup the log with truncate_only, shrink the tlog, and then backup
> the database.
The distribution database's backup model is set to simple. Is this a
problem (except the worse disaster recovery options)?

> Then check your transaction retention period, it should be 48 hours. Make
> sure your distribution clean up job is enabled and running every 10 minutes.
The transaction retention period has been set to the default value
(72h). I changed it to 48h. Then I checked the distribution cleanup job.
It is scheduled to run every 10 minutes. It had been started 5 hours ago
and was still running. I stopped it and started it again. Now it is
running since 15 Minutes. Is it possible that this job lasts more than 5
hours?
Markus
|||It is possible that it could run for more than 5 hours at first. Subsequent
runs should not take as long. Do you have anonymous subscribers? Metadata
hangs around a lot longer for them than for names subscribers.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Markus Renschler" <SP-news@.renschler.net> wrote in message
news:uzVIaOZdFHA.3488@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi Hilary,
> thanks for the advice.
might[vbcol=seagreen]
backup[vbcol=seagreen]
> The distribution database's backup model is set to simple. Is this a
> problem (except the worse disaster recovery options)?
Make[vbcol=seagreen]
minutes.
> The transaction retention period has been set to the default value
> (72h). I changed it to 48h. Then I checked the distribution cleanup job.
> It is scheduled to run every 10 minutes. It had been started 5 hours ago
> and was still running. I stopped it and started it again. Now it is
> running since 15 Minutes. Is it possible that this job lasts more than 5
> hours?
> Markus
|||Hilary Cotter wrote:
> It is possible that it could run for more than 5 hours at first. Subsequent
> runs should not take as long.
It has been running 3:35. The next runs took less than a second, each.
After the cleanup the database was still 22GB in size. I tried to shrink
it, but without an effect.
For testing, I have set the transaction retention period to 1h. Then I
started a distribution database cleanup, but without an effect.

> Do you have anonymous subscribers? Metadata
> hangs around a lot longer for them than for names subscribers.
No, I just have one subscriber which had its subscription pushed from
the origin server (which acts as publisher and distributor).
Could it be helpful if I re-create the distribution database? Is there
any possibility to do this?
Thanks for helping,
Markus

Distributed Transactions between SQL2005 and SQL2000

Hi there,

We have two servers, one (we'll call 'SERVERA') has SQL2005 running on it. The second (we'll call 'YELLOWSTEONE') is running both SQL2000 and SQL2005 on it. The SQL instances on YELLOWSTONE are 'YELLOWSTONE\SQL2000' and 'YELLOWSTONE\SQL2005'. As a linked server, I have an entry for YELLOWSTONE which then links to the SQL Server of YELLOWSTONE\SQL2000 on the server network name of YELLOWSTONE. By them selves they seem to run fine. However, if I have trigger that Runs on SERVERA to do a distributed transaction on 'YELLOWSTONE\SQL2000', I get the following error:

OLE DB provider "SQLNCLI" for linked server "YELLOWSTONE" returned message "Login timeout expired".

OLE DB provider "SQLNCLI" for linked server "YELLOWSTONE" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".

Msg 2, Level 16, State 1, Line 0

Named Pipes Provider: Could not open a connection to SQL Server [2].

If You can provide me any assistance, I would greatly appreciate it. Thanks! - Eric -

Ok, Figured it out. I needed to define the Server type as 'SQL Server' instead of 'Other' and then picking the SQL Server connector. Ooops!