Re-Installation problem (prev installations not removed completely)

I have installed SQL server 2005 on Win SERVER 2003, then uninstalled and then re-installed but I have found out that the previous instances are still listed and the the previous collation too (I have changed reg setting and and language option re-installation).

It looks like that removing program does not remove completely every object, probably registry values

Do you know how to perform a good uninstallation removing everything (add/remove program does not work properly as written before) ?

Any help will be very appreciated.

Thank

After uninstalling SQL Server, check the ARP to confirm that the SQL Server Native Client was also removed. There are a few other support-type components that remain on your box from time to time. This is one of them.

Thanks,
Sam Lester (MSFT)|||

Because some modules are shared among instances on the same machine, I will not be able to unstall the shared modules, like SQL Native Client,etc.

If I had installed several instances of SQL 2005, will I get problems if I uninstall and reinstall some instances later?

NP

Reinitializing a subscription

Win 2000 & SQL 2000 SP3
I have a publication that wants to be reinitialized (The
subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.). When I
created the push subscription, I did it NoSync, so I know I have to
drop and recreate it. But, my question is this....How can I prevent
from loosing the transactions that are pending? If I drop the
subscription & recreate it, the pending transactions will be
lost...right?!?!? I need these. HELP
TIA,
Larry...
Yes you are correct. The best approach to this sort of problem is to use
sp_browsereplcmds like this
sp_browsereplcmds @.publisher_database_id = 7,@.results_table =
'results_table'
where @.publisher_database_id is your publication database ID.
Then you have the commands stored in your results table. You can run these
on your subscriber. You can also use @.xact_seqno_start to define a start id.
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
<lreames@.gmail.com> wrote in message
news:1112196237.338064.299320@.o13g2000cwo.googlegr oups.com...
> Win 2000 & SQL 2000 SP3
> I have a publication that wants to be reinitialized (The
> subscription(s) have been marked inactive and must be reinitialized.
> NoSync subscriptions will need to be dropped and recreated.). When I
> created the push subscription, I did it NoSync, so I know I have to
> drop and recreate it. But, my question is this....How can I prevent
> from loosing the transactions that are pending? If I drop the
> subscription & recreate it, the pending transactions will be
> lost...right?!?!? I need these. HELP
> TIA,
> Larry...
>

reinitialized subscription - more info

Running - Win 2K / SQL 2K
I am constantly, once a week or so,getting an error on a
transactional publication that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
This publication is set up to be continious and is
checked daily to verify it is running. I will come in
one morning and there will be an error. There are 15
remote locations using a transactional/continous
publication to move data to the main office.
How can I prevent this from happening?
What is causing this?
Is there some logging option I can turn on to see more
info about the transactions?
Larry....
By default is a publisher and subscriber have not "talked to" each other for
14 days the subscriber is marked inactive and the subscription may be
dropped. You must reinitialize, regenerate and redistribute the snapshot to
clear this condition.
You can set the interval by right clicking on your publication, selecting
properties and in the subscription expiration section, set a long expiration
value.
I normally run scripts that detect whether the distribution agent has
replicated a transaction to the subscriber in the last 24 hours, and if not,
it raises an alert which causes operations to be paged.
This raises the visibility of these errors.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry..." <anonymous@.discussions.microsoft.com> wrote in message
news:9b3601c43446$63f03c20$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly, once a week or so,getting an error on a
> transactional publication that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> This publication is set up to be continious and is
> checked daily to verify it is running. I will come in
> one morning and there will be an error. There are 15
> remote locations using a transactional/continous
> publication to move data to the main office.
> How can I prevent this from happening?
> What is causing this?
> Is there some logging option I can turn on to see more
> info about the transactions?
> Larry....
>

reinitialized subscription

Running - Win 2K / SQL 2K
I am constantly getting an error on a merge
publication/subscription that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
How can I prevent this from happening?
What is causing this?
Larry...
you normally get this error when your subscribers haven't connected to your
publisher within 14 days for transactional and merge publications.
The way to prevent this is to ensure your subscriber connects to your
publisher within this period.
Exactly how frequently are you getting this error?
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:89a401c432b4$81e001e0$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly getting an error on a merge
> publication/subscription that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> How can I prevent this from happening?
> What is causing this?
> Larry...
|||.....Exactly how frequently are you getting this error?
Hilary,
I get this on one of my continous transactional
subscriptions once every couple of weeks. I check
replication every day and in fact, the SQL server agent
gets restarted every night @. 2:00 am.
Larry...

registering new sql server

Hello,
I have SQL server developer version running on my local workstation.
I recently got a new Win 2003 Box.
Couple of things.
1) IT dept gave me 35 gigs are raid 5. Is this enough for a large DB?
It seems awfully small to me.
2) The SQL server is running all well. In my local Enterprise Manger.
I tried to register a sql server. But I can't get a connect() back.
What could be causing this? I can ping the SQL box because it's on the
same subnet.
Won Lee> 1) IT dept gave me 35 gigs are raid 5. Is this enough for a large DB?
> It seems awfully small to me.
Depends on what you consider a large db. We've got a sql database just over
1 million records spread across 100 tables with that many views and stored
procedures besides, and that's 2gb.
> 2) The SQL server is running all well. In my local Enterprise Manger.
> I tried to register a sql server. But I can't get a connect() back.
> What could be causing this? I can ping the SQL box because it's on the
> same subnet.
Did you set up an alias in the Client Network Utility?|||> 1) IT dept gave me 35 gigs are raid 5. Is this enough for a large DB?
> It seems awfully small to me.
Only you can tell us how large your database is going to be. You need to
research your business requirements and determine size and growth from that.
There's no such thing as a "typical" size for a database.
> I tried to register a sql server. But I can't get a connect() back.
Can you give some more detail. Do you get an error message? Can you verify
in Service Manager that the server is running? Did you supply a valid user
name and password?
This might also help:
http://support.microsoft.com/?id=328306
David Portas
--
Please reply only to the newsgroup
--|||William Morris wrote:
>>1) IT dept gave me 35 gigs are raid 5. Is this enough for a large DB?
>>It seems awfully small to me.
>
> Depends on what you consider a large db. We've got a sql database just over
> 1 million records spread across 100 tables with that many views and stored
> procedures besides, and that's 2gb.
>
Thanks. I looked at the old DB and realized that we only grew at a 3
meg per month rate. I guess the DB is good for awhile.
>>2) The SQL server is running all well. In my local Enterprise Manger.
>>I tried to register a sql server. But I can't get a connect() back.
>>What could be causing this? I can ping the SQL box because it's on the
>>same subnet.
>
> Did you set up an alias in the Client Network Utility?
I didn't do anything. My IT guys set up the box. The error message I'm
getting is, WINBOX-SQL server does not exist or access denied.
I created a user as a DBO owner. I also tried with the SA login
credentials. I can remote desktop into the server and login to the SQL
server through Enterprise Manager and Query Analyzer.
I have no idea what Client Network Utility is so I looked it up in Books
Online. I will give that a try.
BTW How do I find out if they installed the Developer version or the
client/server version of SQL Server 2000?|||> Can you give some more detail. Do you get an error message? Can you verify
> in Service Manager that the server is running? Did you supply a valid user
> name and password?
> This might also help:
> http://support.microsoft.com/?id=328306
>
David,
Yes the service is started. I did created a user and also used the SA
password to login locally.
Thanks for the KB article I will look through it.|||> This might also help:
> http://support.microsoft.com/?id=328306
>
Just in case anyone is insterested.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;306199
A link from the KB article David posted fixed the problem. Funny thing
is that the server is not on DHCP. It was when we first popped it in to
the rack but promptly changed it to a fixed IP address. Kinda funny.
But at least it works now.|||Thanks to William and David for helping me out.
Won Lee