Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts

Friday, March 30, 2012

How can i connect to Sqlserver2000 from sqlserver2005

Hi,

Can any1 tell me how to connect to Sqlserver2000 from sqlserver2005 ...I cant see sqlserver2000 instance name when i try to search in database engine

With regards

mahender

I assume you're talking about using SSMS and you can't see your sql2k instance?

When you click "browse" button, the application send a broadcast onto the network on UDP 1434 to get a list of available sql instances from sqlbrowsers. If the sqlbrowser port is blocked or it's not running on the node where your sql2k instance resides, you would not get a reply back. This does not mean, however, that you cannot connect to your instance. If this is a default instance, you can just specify the servername explicitly and the application (ssms) should connect. If it is a named instance, you will need to specify the listening tcp port (e.g. servername,12345) to connect (this assumes your sqlbrowser is not running).

If you're talking about creating a connection between the two servers, you will want to look for "sp_addlinkedserver" in book online. There should be detailed info to walk you through.

Wednesday, March 21, 2012

How can i attach a SQLServer2005 db to an instance of SQLServer 2000?

i have a db that created in sql2000 and then iattached it to sqlserver 2005 ,now i want to attach this db to sql server 2000 again,but when i do that i get an error message and the attach process fails.plz help me and show me a way to attach this db.

Short answer: you can't :-(
Once you have attached it to SQL Server 2005 it is no longer compatible with the SQL Server 2000 file format.

Monday, February 27, 2012

Hotfix Installation failed on named Instance on a SQL-Server-2000 Cluster

Hi all,
I have a windows 2003 cluster
with sql-server 2000 sp3
and a named instance.
I wanted to installation the hotfix ..859, but the installation failed
and I got the error:
"The logged on account does not have administrator privileges on all
possible owner nodes of the selected SQL Server configuration.
Please log on using an account that has administrator privileges on all
possible owner nodes and then run Hotfix Installer again."
I've checked different things.
My account has the correct rights, the RPC service is running, DNS
works fine ...
I have no idea what to do!
Can someone help?
Greetings
Susn
Are you running the hotfix from the controlling node? Also, you may have to
reboot each node, before the hotfix will install.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
<liebesusn@.web.de> wrote in message
news:1106919750.693602.235970@.f14g2000cwb.googlegr oups.com...
> Hi all,
> I have a windows 2003 cluster
> with sql-server 2000 sp3
> and a named instance.
> I wanted to installation the hotfix ..859, but the installation failed
> and I got the error:
> "The logged on account does not have administrator privileges on all
> possible owner nodes of the selected SQL Server configuration.
> Please log on using an account that has administrator privileges on all
> possible owner nodes and then run Hotfix Installer again."
> I've checked different things.
> My account has the correct rights, the RPC service is running, DNS
> works fine ...
> I have no idea what to do!
> Can someone help?
> Greetings
> Susn
>
|||Hi Rod,
yes, the hotfix was running from the controlling node and both nodes
was rebooted.
Any other idea?
Greetings Susn
|||No, that about does it for me, sorry!
Rod
"Susn" <liebesusn@.web.de> wrote in message
news:1107160932.634056.6880@.c13g2000cwb.googlegrou ps.com...
> Hi Rod,
> yes, the hotfix was running from the controlling node and both nodes
> was rebooted.
> Any other idea?
> Greetings Susn
>
|||Hi Susn,
Just wondering if you were able to install the hotfix. I would recommend you to log into both the nodes of the cluster with the startup account of the clustered SQL Server service (this account is a doman account and
should have all the required rights). Then start the hotfix installation on the node where SQL Server instance is currently running.
Keep up updated. If it fails, then please post the log for the hotfix failure.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx