Rejoining two broken replicating servers

We had a two-site system go badly wrong as a result of something. The net
result of this was that the publisher had to be completely reformatted and
reinstalled. The server has, as a result of this, been given a different
name (went from being a named instance to not being one).
Currently the publisher doesn't know it's a replicating system.
Is there any way to join these two together so that they just start
from where they left off, or will I have to re-do all the replication
from scratch by various SELECT INTOs to get the data across, then
pushing out fresh subscriptions?
Thanks,
Jim
Find me at http://www.ursaMinorBeta.co.uk
JediGeeks http://www.jedigeeks.com
"There's no 'I' in team, but there is a 'me' if you jumble
the letters up a bit." - Dr. House.
Jim,
I'm hoping you have you got a copy of your replication scripts? If so, I'd
alter the server name in the scripts and then set things up from scratch by
initializing the subscribers. There's no need to do select intos - the
odbcbcp will take care of the initial data flow.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||In article <OZP8o$qvFHA.1648@.TK2MSFTNGP10.phx.gbl>, Paul Ibison wrote:
> Jim,
> I'm hoping you have you got a copy of your replication scripts? If so, I'd
> alter the server name in the scripts and then set things up from scratch by
> initializing the subscribers. There's no need to do select intos - the
> odbcbcp will take care of the initial data flow.
> Cheers,
Forgive me, but which scripts are these?
I'm a bit new at this sort of low-level tinkering :-)
Jim
Find me at http://www.ursaMinorBeta.co.uk
JediGeeks http://www.jedigeeks.com
"There's no 'I' in team, but there is a 'me' if you jumble
the letters up a bit." - Dr. House.
|||Jim,
I make regular backups of my replication setup - (see
http://www.replicationanswers.com/Script7.asp). If you don't have these,
you'll might still try running my script to see if you can generate them on
your renamed database - bit of a longshot but worth a try. Next thing to try
is to restore the database to it's original name and run hte script.
Finally, restore this database, msdb and the distribution database then run
the script. I can't test this right now, but please let me know how it goes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Rejoining replicating servers

We had a two-site system go badly wrong as a result of something. The net
result of this was that the publisher had to be completely reformatted and
reinstalled. The server has, as a result of this, been given a different
name (went from being a named instance to not being one).

Currently the publisher doesn't know it's a replicating system.

Is there any way to join these two together so that they just start
from where they left off, or will I have to re-do all the replication
from scratch by various SELECT INTOs to get the data across, then
pushing out fresh subscriptions?

Thanks,

Jim
--
Find me at http://www.ursaMinorBeta.co.uk
JediGeeks http://www.jedigeeks.com
"There's no 'I' in team, but there is a 'me' if you jumble
the letters up a bit." - Dr. House.You might get a better response in
microsoft.public.sqlserver.replication.

Simon|||In article <1127313805.460090.79830@.g14g2000cwa.googlegroups.c om>, Simon Hayes wrote:
> You might get a better response in
> microsoft.public.sqlserver.replication.

Thanks.

Jim
--
Find me at http://www.ursaMinorBeta.co.uk
JediGeeks http://www.jedigeeks.com
"There's no 'I' in team, but there is a 'me' if you jumble
the letters up a bit." - Dr. House.

Reinitialize replication - Merge

I have a few databases that I replicate between NY and Greece. We utilize merge replication on all SQL 2000 servers. My question, is there a quick way to reinitialize replication besides pushing the initial snapshot? I would like to avoid the initial snapshot in the event of a failure due to the amount of time it takes to transfer over our 3mb ATM circuit.

Any help is greatly appreciated.

Thanks,
MichaelYou are kind of between a rock and a hard place (as you've probably noticed). The problem is that if you don't know what is "out of whack" in the replica, the only way to get it back in sync is to push a new snapshot. If you know what the problem is, replication prevents you from fixing it!

In the case where you don't know what is broken, the snapshot is your only safe answer. It may be ugly, but it saves everything that can be salvaged.

In the case where you know what needs to be fixed, you can drop the subscription, fix the problems, then resubscribe without pushing a new snapshot.

See the notes on this subject in MSDN (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replimpl_7xbn.asp).

-PatP|||Usally you call ReinitializeSubscription when you want to recreate all the
tables on the subscriber and start from a "clean" state. Note that calling ReinitializeSubscription would not clean your subscribtion. This will happen on on the next sync.

Refer to books online for further information on merge replication topic.

Re-indexing table causes Windows to re-boot !

I have a DB with multiple tables and when I attempt to index one of the
tables the whole Windows servers crashes and reboots. My understanding is
that SQLServer should run as an isolated application and so should not be
able to affect the operating system.
This server has been fine for over a year now but has just started to
exhibit this problem (no recent changes or updates to the server, apart from
regular anti-virus updates, that could account for this behaviour).
The problem in more detail:
Database - 1577MB data (518 MB free). Set to automatically grow at 10% to
an un-restricted limit (data and log)
Table in question - 900808 KB data, ~7000000 rows of data
Indexes - there are three "user" indexes that I create. One of them is a
clustered index. When any of these indexes is built the server crashes.
Exhaustive DBCC tests imply that the DB and table are in perfect health.
Nothing in the event log and no memory dumps.
SQLServer - SQLServer 2000 sp3a
Windows - Win2000 sp3, IBM XSERIES_335 with 3 GHz xeon processor and oodles
of memory.
User - at wits end
Any advice would be most welcome
Thanks
GriffGriff,
You are correct. You should focus on the operating system. Most likely SQL
Server is just taxing the IO or Processor hard and there is either a
hardware or driver issue. In the event log is it an unexpected reboot or is
there a stop error listed?
"Griff" <Howling@.The.Moon> wrote in message
news:%234bILC2vFHA.2556@.TK2MSFTNGP15.phx.gbl...
>I have a DB with multiple tables and when I attempt to index one of the
>tables the whole Windows servers crashes and reboots. My understanding is
>that SQLServer should run as an isolated application and so should not be
>able to affect the operating system.
> This server has been fine for over a year now but has just started to
> exhibit this problem (no recent changes or updates to the server, apart
> from regular anti-virus updates, that could account for this behaviour).
> The problem in more detail:
> Database - 1577MB data (518 MB free). Set to automatically grow at 10% to
> an un-restricted limit (data and log)
> Table in question - 900808 KB data, ~7000000 rows of data
> Indexes - there are three "user" indexes that I create. One of them is a
> clustered index. When any of these indexes is built the server crashes.
> Exhaustive DBCC tests imply that the DB and table are in perfect health.
> Nothing in the event log and no memory dumps.
> SQLServer - SQLServer 2000 sp3a
> Windows - Win2000 sp3, IBM XSERIES_335 with 3 GHz xeon processor and
> oodles of memory.
> User - at wits end
> Any advice would be most welcome
> Thanks
> Griff
>
>|||Having read the event logs (application, system, security & SQLServer
ones) and searched for a memory dmp file I get the impression that the
server crashed so fast that it simply didn't have the chance to log
anything. Metaphorically speaking, it had the rug pulled from under
it.
The event log simply lists the fact that it rebooted after an
unexpected system shutdown, but I can't find anything that implies what
could have caused the system shutdown.
Watching the task manager whilst the re-indexing is occuring (before it
dies), it shows no real sign of taxing the server's resources. Of
course now, running live without indexes, the server is as slow as a
lame dog, presumably because SQLServer is having to do lots of full
table scans.|||Oddly enough I've seen this scenerio with two of our 32 way servers. We and
the hardware vendor were able to reproduce the system fault but the vendor
never could tell us what was wrong or how to fix it. Basically when the
server approached 100% CPU (doing masive qeries) the system started geting
dirty memory transfers between pods. It all started after we upgraded our
SQL Server 2000 build. We switched to 64 bit HP servers and immediately
stopped experiencing the issue. Assuming a good power supply, in my opinion
any unexpected reboot on a Windows server is one of three things.
From most likely to least likely:
1. A hardware issue
2. A poorly written driver in kernal mode
3. Windows not trapping the error.
SQL Server may be pushing the system in a new way or to 100% but that would
be a performance issue not an availability issue.
Good luck.
"Griff" <griffithsj_520@.hotmail.com> wrote in message
news:1127390278.062254.254300@.g49g2000cwa.googlegroups.com...
> Having read the event logs (application, system, security & SQLServer
> ones) and searched for a memory dmp file I get the impression that the
> server crashed so fast that it simply didn't have the chance to log
> anything. Metaphorically speaking, it had the rug pulled from under
> it.
> The event log simply lists the fact that it rebooted after an
> unexpected system shutdown, but I can't find anything that implies what
> could have caused the system shutdown.
> Watching the task manager whilst the re-indexing is occuring (before it
> dies), it shows no real sign of taxing the server's resources. Of
> course now, running live without indexes, the server is as slow as a
> lame dog, presumably because SQLServer is having to do lots of full
> table scans.
>|||Well, I can't say what the problem was, but we do appear to have fixed it.
Despite nothing "appearing" to have changed on the system (we manually apply
the Microsoft critical upgrades), this problem started occuring out of the
blue.
However, it got worse throughout the day - the server started rebooting
during "normal" use, approximately ever 30 minutes. As mentioned
previously, the CPU was more or less at 100% because we couldn't rebuild the
indexes, so I was wondering whether it could be overheating or some other
symptom of the hardware being over-stressed (though it's a good spec server
so should cope).
Anyhow, that evening we clutched at straws and applied Win2000 sp4 (had been
sp3) and, would you believe it, it fixed the problem and a good nights sleep
was had by all.|||Griff wrote:
> Well, I can't say what the problem was, but we do appear to have
> fixed it.
> Despite nothing "appearing" to have changed on the system (we
> manually apply the Microsoft critical upgrades), this problem started
> occuring out of the blue.
> However, it got worse throughout the day - the server started
> rebooting during "normal" use, approximately ever 30 minutes. As
> mentioned previously, the CPU was more or less at 100% because we
> couldn't rebuild the indexes, so I was wondering whether it could be
> overheating or some other symptom of the hardware being over-stressed
> (though it's a good spec server so should cope).
> Anyhow, that evening we clutched at straws and applied Win2000 sp4
> (had been sp3) and, would you believe it, it fixed the problem and a
> good nights sleep was had by all.
Probably someone was "joking": there are some holes in some windows
versions which allow a host to be restarted / switched off or similar via
network (these are usually closed by sp4 IIRC). So it could even be
manual intervention that caused this...
Kind regards
robert|||Hi Robert
I believe that we can almost rule that one out. The server is behind a
firewall that only allows HTTP in from unknown IP addresses, everything else
is effectively blocked. The only person who can connect to it in any other
way is me.
But hey, we know that the only way to make a computer completely safe is to
switch it off.

Registration of SQL Servers missing in Enterprise manager

Hi All,
Recently a strange behaviour was seen with Enterprise manager. When we
change the Windows login password all the registrations of SQL Servers are
missing from SQL Server Enterprise Manager. Did anyone faced this situatio
n
before? Its really painful to register 20 servers each time when login
password is changed. Some of the registered servers are windows
authentication and rest of them are SQL Server authentication.
Thanks a lot in advance!
Vinod MeesalaHi,
Never aware of this issues. What is the SQL Server service pack you are usin
g?
If you are using old service packs, install SP4 for SQL 2000 (if you are
using SQL Server 2000) and see if you still have issues.
Thanks
Hari
SQL Server MVP
"VM" wrote:

> Hi All,
> Recently a strange behaviour was seen with Enterprise manager. When we
> change the Windows login password all the registrations of SQL Servers are
> missing from SQL Server Enterprise Manager. Did anyone faced this situat
ion
> before? Its really painful to register 20 servers each time when login
> password is changed. Some of the registered servers are windows
> authentication and rest of them are SQL Server authentication.
> Thanks a lot in advance!
> Vinod Meesala|||Sounds like this may be the issue you are running into:
FIX: Registered remote servers disappear from SQL Enterprise
Manager in Windows XP when user password is changed
http://support.microsoft.com/?id=323280
-Sue
On Thu, 17 Aug 2006 13:39:02 -0700, VM
<VM@.discussions.microsoft.com> wrote:

>Hi All,
>Recently a strange behaviour was seen with Enterprise manager. When we
>change the Windows login password all the registrations of SQL Servers are
>missing from SQL Server Enterprise Manager. Did anyone faced this situati
on
>before? Its really painful to register 20 servers each time when login
>password is changed. Some of the registered servers are windows
>authentication and rest of them are SQL Server authentication.
>Thanks a lot in advance!
>Vinod Meesala|||Sue,
Thats an awsome piece of information. I wasn't aware of this.
Thanks
Hari
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:04s9e214f3pk9386bmg12lq7jq8q4kbqhj@.
4ax.com...
> Sounds like this may be the issue you are running into:
> FIX: Registered remote servers disappear from SQL Enterprise
> Manager in Windows XP when user password is changed
> http://support.microsoft.com/?id=323280
> -Sue
> On Thu, 17 Aug 2006 13:39:02 -0700, VM
> <VM@.discussions.microsoft.com> wrote:
>
>|||Hey Hari,
People haven't hit the issue for quite awhile so you
probably just forgot it by now. I think it was two or three
years ago when people posted hitting the issue. I guess I'm
just wasting limited brain space with old info - your brain
is just more current than mine : )
-Sue
On Thu, 17 Aug 2006 19:00:43 -0500, "Hari Prasad"
<hari_prasad_k@.hotmail.com> wrote:

>Sue,
>Thats an awsome piece of information. I wasn't aware of this.
>Thanks
>Hari
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:04s9e214f3pk9386bmg12lq7jq8q4kbqhj@.
4ax.com...
>|||Excellent Finding!! Thanks much Sue! I will try this Fix.
Vinod Meesala
"Sue Hoegemeier" wrote:

> Sounds like this may be the issue you are running into:
> FIX: Registered remote servers disappear from SQL Enterprise
> Manager in Windows XP when user password is changed
> http://support.microsoft.com/?id=323280
> -Sue
> On Thu, 17 Aug 2006 13:39:02 -0700, VM
> <VM@.discussions.microsoft.com> wrote:
>
>

Registration of SQL Servers missing in Enterprise manager

Hi All,
Recently a strange behaviour was seen with Enterprise manager. When we
change the Windows login password all the registrations of SQL Servers are
missing from SQL Server Enterprise Manager. Did anyone faced this situation
before? Its really painful to register 20 servers each time when login
password is changed. Some of the registered servers are windows
authentication and rest of them are SQL Server authentication.
Thanks a lot in advance!
Vinod MeesalaHi,
Never aware of this issues. What is the SQL Server service pack you are using?
If you are using old service packs, install SP4 for SQL 2000 (if you are
using SQL Server 2000) and see if you still have issues.
Thanks
Hari
SQL Server MVP
"VM" wrote:
> Hi All,
> Recently a strange behaviour was seen with Enterprise manager. When we
> change the Windows login password all the registrations of SQL Servers are
> missing from SQL Server Enterprise Manager. Did anyone faced this situation
> before? Its really painful to register 20 servers each time when login
> password is changed. Some of the registered servers are windows
> authentication and rest of them are SQL Server authentication.
> Thanks a lot in advance!
> Vinod Meesala|||Sounds like this may be the issue you are running into:
FIX: Registered remote servers disappear from SQL Enterprise
Manager in Windows XP when user password is changed
http://support.microsoft.com/?id=323280
-Sue
On Thu, 17 Aug 2006 13:39:02 -0700, VM
<VM@.discussions.microsoft.com> wrote:
>Hi All,
>Recently a strange behaviour was seen with Enterprise manager. When we
>change the Windows login password all the registrations of SQL Servers are
>missing from SQL Server Enterprise Manager. Did anyone faced this situation
>before? Its really painful to register 20 servers each time when login
>password is changed. Some of the registered servers are windows
>authentication and rest of them are SQL Server authentication.
>Thanks a lot in advance!
>Vinod Meesala|||Sue,
Thats an awsome piece of information. I wasn't aware of this.
Thanks
Hari
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:04s9e214f3pk9386bmg12lq7jq8q4kbqhj@.4ax.com...
> Sounds like this may be the issue you are running into:
> FIX: Registered remote servers disappear from SQL Enterprise
> Manager in Windows XP when user password is changed
> http://support.microsoft.com/?id=323280
> -Sue
> On Thu, 17 Aug 2006 13:39:02 -0700, VM
> <VM@.discussions.microsoft.com> wrote:
>>Hi All,
>>Recently a strange behaviour was seen with Enterprise manager. When we
>>change the Windows login password all the registrations of SQL Servers are
>>missing from SQL Server Enterprise Manager. Did anyone faced this
>>situation
>>before? Its really painful to register 20 servers each time when login
>>password is changed. Some of the registered servers are windows
>>authentication and rest of them are SQL Server authentication.
>>Thanks a lot in advance!
>>Vinod Meesala
>|||Hey Hari,
People haven't hit the issue for quite awhile so you
probably just forgot it by now. I think it was two or three
years ago when people posted hitting the issue. I guess I'm
just wasting limited brain space with old info - your brain
is just more current than mine : )
-Sue
On Thu, 17 Aug 2006 19:00:43 -0500, "Hari Prasad"
<hari_prasad_k@.hotmail.com> wrote:
>Sue,
>Thats an awsome piece of information. I wasn't aware of this.
>Thanks
>Hari
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:04s9e214f3pk9386bmg12lq7jq8q4kbqhj@.4ax.com...
>> Sounds like this may be the issue you are running into:
>> FIX: Registered remote servers disappear from SQL Enterprise
>> Manager in Windows XP when user password is changed
>> http://support.microsoft.com/?id=323280
>> -Sue
>> On Thu, 17 Aug 2006 13:39:02 -0700, VM
>> <VM@.discussions.microsoft.com> wrote:
>>Hi All,
>>Recently a strange behaviour was seen with Enterprise manager. When we
>>change the Windows login password all the registrations of SQL Servers are
>>missing from SQL Server Enterprise Manager. Did anyone faced this
>>situation
>>before? Its really painful to register 20 servers each time when login
>>password is changed. Some of the registered servers are windows
>>authentication and rest of them are SQL Server authentication.
>>Thanks a lot in advance!
>>Vinod Meesala
>|||Excellent Finding!! Thanks much Sue! I will try this Fix.
Vinod Meesala
"Sue Hoegemeier" wrote:
> Sounds like this may be the issue you are running into:
> FIX: Registered remote servers disappear from SQL Enterprise
> Manager in Windows XP when user password is changed
> http://support.microsoft.com/?id=323280
> -Sue
> On Thu, 17 Aug 2006 13:39:02 -0700, VM
> <VM@.discussions.microsoft.com> wrote:
> >Hi All,
> >
> >Recently a strange behaviour was seen with Enterprise manager. When we
> >change the Windows login password all the registrations of SQL Servers are
> >missing from SQL Server Enterprise Manager. Did anyone faced this situation
> >before? Its really painful to register 20 servers each time when login
> >password is changed. Some of the registered servers are windows
> >authentication and rest of them are SQL Server authentication.
> >
> >Thanks a lot in advance!
> >
> >Vinod Meesala
>

Registration of SQL Server

Helo All,
We have two W2K servers. One is an SQL Server(S1) and another one is a
server (S2) on which SSL Certificate is installed.
When I try to register SQL Server from S2 through enterprises manager,
following error occured:
Encryption not supported on SQL Server| ConnectionOpen(PreLoginHandshake...
In this scenario is it mandatory to have SSL installed on the SQL Server
Machine (S1) also?
Any comment on this would be highly helpful.
Thanks in anticipation!
Warm Regards
Sathian>
> We have two W2K servers. One is an SQL Server(S1) and another one is a
> server (S2) on which SSL Certificate is installed.
> When I try to register SQL Server from S2 through enterprises manager,
> following error occured:
> Encryption not supported on SQL Server|
ConnectionOpen(PreLoginHandshake...
> In this scenario is it mandatory to have SSL installed on the SQL Server
> Machine (S1) also?
> Any comment on this would be highly helpful.
--
This error indicates either sql server server thinks the certificate is
invalid
or can't locate the certificate. To check if Sql Server can use a
certificate, enable
force protocol encryption on the server side and restart the service. If
Sql Server starts then certificate is okay.
The error can also occur if you have installed the certificate on sql
server but
have not restarted sql. so even if you are using client side encryption,
you need to restart sql server once the certificate is installed.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Registration of SQL Server

Helo All,
We have two W2K servers. One is an SQL Server(S1) and another one is a
server (S2) on which SSL Certificate is installed.
When I try to register SQL Server from S2 through enterprises manager,
following error occured:
Encryption not supported on SQL Server| ConnectionOpen(PreLoginHandshake...
In this scenario is it mandatory to have SSL installed on the SQL Server
Machine (S1) also?
Any comment on this would be highly helpful.
Thanks in anticipation!
Warm Regards
Sathian
>
> We have two W2K servers. One is an SQL Server(S1) and another one is a
> server (S2) on which SSL Certificate is installed.
> When I try to register SQL Server from S2 through enterprises manager,
> following error occured:
> Encryption not supported on SQL Server|
ConnectionOpen(PreLoginHandshake...
> In this scenario is it mandatory to have SSL installed on the SQL Server
> Machine (S1) also?
> Any comment on this would be highly helpful.
This error indicates either sql server server thinks the certificate is
invalid
or can't locate the certificate. To check if Sql Server can use a
certificate, enable
force protocol encryption on the server side and restart the service. If
Sql Server starts then certificate is okay.
The error can also occur if you have installed the certificate on sql
server but
have not restarted sql. so even if you are using client side encryption,
you need to restart sql server once the certificate is installed.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Registers 2000 Servers in SS 2005 Management Console

We just set up our first server with SS 2005, and I am getting familiar with the Management Console layout and features. Can someone confirm for me if I can register my SS 2000 databases within the 2005 Management Console and work within that environment on those systems, or whether that will have any consequences or cause harm to the 2000 systems?

Thanks

Judy

Yes you can, and SQL Server 2000 is fully supported as being administered from SQL Server 2005 management studio.|||

Thanks so much Richard. I appreciate the fast reply.

Judy

Registering SQL Server

I m having 2 servers i wansted register the SQL server at one node
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
Yousuf Khan
Programmer
Hi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:

> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer
|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
Yousuf Khan
Programmer
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctly
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:

Registering SQL Server

I m having 2 servers i wansted register the SQL server at one node
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
--
Yousuf Khan
ProgrammerHi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:

> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
--
Yousuf Khan
Programmer
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctl
y
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:
>

Registering SQL Server

I m having 2 servers i wansted register the SQL server at one node
when i m registering the SQL server through SQL enterprises it showing the
error
"Unable to connect the sql server unavailable of does not exist"
what can be the problem
--
Yousuf Khan
ProgrammerHi
You could have typed in the wrong name, the server is not using the
protocols you have configured or ports/permissions are not set up correctly
to allow you to connect e.g. a firewall or restricted account.
Can you connect using Query Analyser?
You may want to try specifying the IP address instead if the name?
John
"Yousuf" wrote:
> I m having 2 servers i wansted register the SQL server at one node
> when i m registering the SQL server through SQL enterprises it showing the
> error
> "Unable to connect the sql server unavailable of does not exist"
> what can be the problem
> --
> Yousuf Khan
> Programmer|||both the systems are using the same prtocols(NetBeui) and i dont have any
firwall
both systems are having win nt and i m able to make turusties for each other
but not able to connect sql
--
Yousuf Khan
Programmer
"John Bell" wrote:
> Hi
> You could have typed in the wrong name, the server is not using the
> protocols you have configured or ports/permissions are not set up correctly
> to allow you to connect e.g. a firewall or restricted account.
> Can you connect using Query Analyser?
> You may want to try specifying the IP address instead if the name?
> John
>
> "Yousuf" wrote:
> > I m having 2 servers i wansted register the SQL server at one node
> > when i m registering the SQL server through SQL enterprises it showing the
> > error
> > "Unable to connect the sql server unavailable of does not exist"
> > what can be the problem
> > --
> > Yousuf Khan
> > Programmer|||Hi,
Can you connect to an administrative share eg \\server_name\c$ ?
Can you launch Enterprise Manager on the server and connect to the local
instance? Can you connect EM on one SQL Server to the other SQL Server?
Do you know which network library SQL Server is using? I didn't know that
it could use NetBEUI so if the servers are communicating only on NetBEUI and
SQL Server is communicating on Named Pipes or TCP/IP, might this not cause a
problem?
Cheers,
IM|||I am able to conncet to local machine EM not able to other server, i am using
netbeui protocol through Win NT i m getting his share and users but not
getting conneted to sql server
--
Yousuf Khan
Programmer
"Ian Murphy" wrote:
> Hi,
> Can you connect to an administrative share eg \\server_name\c$ ?
> Can you launch Enterprise Manager on the server and connect to the local
> instance? Can you connect EM on one SQL Server to the other SQL Server?
> Do you know which network library SQL Server is using? I didn't know that
> it could use NetBEUI so if the servers are communicating only on NetBEUI and
> SQL Server is communicating on Named Pipes or TCP/IP, might this not cause a
> problem?
> Cheers,
> IM

Registering servers in Enterprise Manager.

Is there any way I can reload the list of servers I
registered through Enterprise Manager, so that I don't
have to register them manually. I have approx. 80 servers
registered with Enterprise manager on my old workstation
and now I want them on my new workstation.
Or to put this question otherway: where does enterprise
manager store the information of servers registered with
it?
Any suggestions welcome. Thanks. -- Adi ..you can use
sp_addlinkedserver (parms)
in the query analyzer
"Adi" <adibazz_nospam@.hotmail.com> wrote in message
news:6caf01c35867$6610d200$a001280a@.phx.gbl...
> Is there any way I can reload the list of servers I
> registered through Enterprise Manager, so that I don't
> have to register them manually. I have approx. 80 servers
> registered with Enterprise manager on my old workstation
> and now I want them on my new workstation.
> Or to put this question otherway: where does enterprise
> manager store the information of servers registered with
> it?
> Any suggestions welcome. Thanks. -- Adi ..|||What do you use to manage these 80 servers please. I will
like to know.
Thanks,
Aboki.
>--Original Message--
>Is there any way I can reload the list of servers I
>registered through Enterprise Manager, so that I don't
>have to register them manually. I have approx. 80 servers
>registered with Enterprise manager on my old workstation
>and now I want them on my new workstation.
>Or to put this question otherway: where does enterprise
>manager store the information of servers registered with
>it?
>Any suggestions welcome. Thanks. -- Adi ..
>.
>|||Thanks for your reply but I am talking here for
registering the server (and that through Enterprise
Manager). -- Adi ..
>--Original Message--
>you can use
>sp_addlinkedserver (parms)
>in the query analyzer
>"Adi" <adibazz_nospam@.hotmail.com> wrote in message
>news:6caf01c35867$6610d200$a001280a@.phx.gbl...
>> Is there any way I can reload the list of servers I
>> registered through Enterprise Manager, so that I don't
>> have to register them manually. I have approx. 80
servers
>> registered with Enterprise manager on my old workstation
>> and now I want them on my new workstation.
>> Or to put this question otherway: where does enterprise
>> manager store the information of servers registered with
>> it?
>> Any suggestions welcome. Thanks. -- Adi ..
>
>.
>|||if you want do batch mode then instead of using the enterprise manager you
use the query analyzer and use the Sp.
if you use the enterprise you need to do manually, one at a time.
"Adi." <adibazz_nospam@.hotmail.com> wrote in message
news:01d701c3586f$8b7e9a10$a601280a@.phx.gbl...
> Thanks for your reply but I am talking here for
> registering the server (and that through Enterprise
> Manager). -- Adi ..
> >--Original Message--
> >you can use
> >sp_addlinkedserver (parms)
> >
> >in the query analyzer
> >
> >"Adi" <adibazz_nospam@.hotmail.com> wrote in message
> >news:6caf01c35867$6610d200$a001280a@.phx.gbl...
> >> Is there any way I can reload the list of servers I
> >> registered through Enterprise Manager, so that I don't
> >> have to register them manually. I have approx. 80
> servers
> >> registered with Enterprise manager on my old workstation
> >> and now I want them on my new workstation.
> >>
> >> Or to put this question otherway: where does enterprise
> >> manager store the information of servers registered with
> >> it?
> >>
> >> Any suggestions welcome. Thanks. -- Adi ..
> >
> >
> >.
> >

Registering Servers

In Enterprise Manager 2000 I was able to register multiple servers and next
time I opened it those servers would automatically connect. With SQL Server
Management Studio 2005 I can register multiple servers, but next time I open
it only the last one I had connected shows. Is there a way to maintain
multiple connections?
Hi Gary
I believe the object browser will show the server that you have logged into,
you will need to log into the other servers to get them in object explorer.
You want to raise this as an request at
http://lab.msdn.microsoft.com/produc...k/default.aspx
John
"Gary L" wrote:

> In Enterprise Manager 2000 I was able to register multiple servers and next
> time I opened it those servers would automatically connect. With SQL Server
> Management Studio 2005 I can register multiple servers, but next time I open
> it only the last one I had connected shows. Is there a way to maintain
> multiple connections?

registering servers

Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanks
jonjo,
This won't affect any clients - just your local machine. It takes
seconds to do and is quite safe.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
jonjo wrote:
> Hi
> I have to set up replication but the server is registered in EM as 'local'
> so I need to delete this registration and then re-register with the correct
> name. My question is in the time between deleting the old registration, and
> then registering the new one, will the dbs still be available to any clients
> wishing to connect?
> Thanks
|||SQLEM is and administrative client API, but it is still just a client. That
is, it is localized the user and/or workstation that hosts the installation,
not the DBMS.
Sincerely,
Anthony Thomas

"jonjo" <jonjo@.discussions.microsoft.com> wrote in message
news:B04A35E0-D628-49AA-A6D8-E70BF976D8F3@.microsoft.com...
Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanks

registering servers

Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanksjonjo,
This won't affect any clients - just your local machine. It takes
seconds to do and is quite safe.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
jonjo wrote:
> Hi
> I have to set up replication but the server is registered in EM as 'local'
> so I need to delete this registration and then re-register with the correc
t
> name. My question is in the time between deleting the old registration, an
d
> then registering the new one, will the dbs still be available to any clien
ts
> wishing to connect?
> Thanks|||SQLEM is and administrative client API, but it is still just a client. That
is, it is localized the user and/or workstation that hosts the installation,
not the DBMS.
Sincerely,
Anthony Thomas
"jonjo" <jonjo@.discussions.microsoft.com> wrote in message
news:B04A35E0-D628-49AA-A6D8-E70BF976D8F3@.microsoft.com...
Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanks

Registering Servers

In Enterprise Manager 2000 I was able to register multiple servers and next
time I opened it those servers would automatically connect. With SQL Server
Management Studio 2005 I can register multiple servers, but next time I open
it only the last one I had connected shows. Is there a way to maintain
multiple connections?Hi Gary
I believe the object browser will show the server that you have logged into,
you will need to log into the other servers to get them in object explorer.
You want to raise this as an request at
http://lab.msdn.microsoft.com/produ...ck/default.aspx
John
"Gary L" wrote:

> In Enterprise Manager 2000 I was able to register multiple servers and nex
t
> time I opened it those servers would automatically connect. With SQL Serv
er
> Management Studio 2005 I can register multiple servers, but next time I op
en
> it only the last one I had connected shows. Is there a way to maintain
> multiple connections?

Registering Servers

In Enterprise Manager 2000 I was able to register multiple servers and next
time I opened it those servers would automatically connect. With SQL Server
Management Studio 2005 I can register multiple servers, but next time I open
it only the last one I had connected shows. Is there a way to maintain
multiple connections?Hi Gary
I believe the object browser will show the server that you have logged into,
you will need to log into the other servers to get them in object explorer.
You want to raise this as an request at
http://lab.msdn.microsoft.com/productfeedback/default.aspx
John
"Gary L" wrote:
> In Enterprise Manager 2000 I was able to register multiple servers and next
> time I opened it those servers would automatically connect. With SQL Server
> Management Studio 2005 I can register multiple servers, but next time I open
> it only the last one I had connected shows. Is there a way to maintain
> multiple connections?

registering servers

Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanksjonjo,
This won't affect any clients - just your local machine. It takes
seconds to do and is quite safe.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
jonjo wrote:
> Hi
> I have to set up replication but the server is registered in EM as 'local'
> so I need to delete this registration and then re-register with the correct
> name. My question is in the time between deleting the old registration, and
> then registering the new one, will the dbs still be available to any clients
> wishing to connect?
> Thanks|||SQLEM is and administrative client API, but it is still just a client. That
is, it is localized the user and/or workstation that hosts the installation,
not the DBMS.
Sincerely,
Anthony Thomas
"jonjo" <jonjo@.discussions.microsoft.com> wrote in message
news:B04A35E0-D628-49AA-A6D8-E70BF976D8F3@.microsoft.com...
Hi
I have to set up replication but the server is registered in EM as 'local'
so I need to delete this registration and then re-register with the correct
name. My question is in the time between deleting the old registration, and
then registering the new one, will the dbs still be available to any clients
wishing to connect?
Thanks

Registering by massive way sql servers

hi everyone,
Imagine you have 20 workstations and for each of them you've got to register
by MMC around 30 sql servers. It's stupid to imagine do a registered one by
one if you know that all of them have the same password and overall, you hav
e
a list containing the IP's
file:
10.0.12.1 user tr1
10.0.12.2 user tr1
...
Sql25k is coming but not yet...
Thanks in advance,
--
Please post DDL, DCL and DML statements as well as any error message in
order to understand better your request. It''''s hard to provide information
without seeing the code. location: Alicante (ES)why do you need to register all the workstations on all the servers? if
you're doing things on all workstations from all servers I would have
thought you'd be scripting out changes anyway.|||Found this on the web; use VBScript and SQLDMO:
http://www.wardyit.com/blog/blog/ar...6/02/18/85.aspx
HTH,
Stu|||thanks to both
--
Please post DDL, DCL and DML statements as well as any error message in
order to understand better your request. It''''s hard to provide information
without seeing the code. location: Alicante (ES)
"Stu" wrote:

> Found this on the web; use VBScript and SQLDMO:
> http://www.wardyit.com/blog/blog/ar...6/02/18/85.aspx
> HTH,
> Stu
>