We have a client running a 3rd party app on sql 2000 Enterprise on Windows 2003 Advanced attached to a new SAN. They are looking at adding another SQL server and clustering for failover. Anyone done this before. Do you have to reninstall sql server on the original box to do this. This a a heavily used app, so downtime is always an issue.
I have an instance VSdotNet for SQL Server 2000 on my machine. Now I want to create another instance called NetSDK, so that the NetSDK and VSdotNet exist side by side.
I need to move a large number of reports from a 2000 reporting services install to 2005. I've used the RS Scripter utility with some success. The issue I'm having is migrating history.
Can history be migrated without upgrading the reportserver and temp db to 2005? We'd like to preserve our 2000 environment while we move...although I suppose we could create another RS instance and copy the database, do the upgrade - but how would we merge our existing 2005 install with the upgraded 2000.
Given than once SQL Server 2005 is installed, SQL Server Studio has to be used instead of Enterprise manager, can both SQL 2000 and 2005 be used on the same machine, be it development or production? (The second one to be installed probably would be a named instance.) Any experiance of doing this or a pointer to a Microsoft recommendation would be appreciated.
(1) Can we create Default Instance & Named Instance in the clustering environment (i.e.) two instances in clustering on same hardware.
The idea here is , to put some highly transactional databases on default instance ( and giving 5 CPU's to Default instance ) and on the Named Instance ( giving 3 CPU's for Named Instance) in CLUSTERING ENVIRONMENT.
(2) Can anyone guide me , how can we restrict the instances to take 5 Cpu's & 3 Cpu's repectively Iin CLUSTERING ENVIRONMENT.
I am trying to set up a Named Instance of SQL 2000 on the same machine that has a default instance of SQL 7.0. The setup always completes and I am able to register the Named Instance of the SQL Server with which it was installed on. However, when I try to connect the users to the database, with both windows and SQL authentication, I receive a SQL server not found error. I have tried an alias setup as well as physically specifying the port number in settup up an ODBC connection. Has anyone ran into similar problems? Also, has anyone been able to successfully complete the process as mentioned above?
We have a SQL 2008 Instance existing on active/passive cluster with 2 nodes running on Windows server 2008 R2 Ent. Edn.
Now we need to install another SQL instance on this cluster. So what are the prerequisites apart from new IP address? Do we need shared disks or can the existing disks can be utilized?
I have an existing instance of sql express 2005 w/advanced services installed. When I installed I did not install full text search. Is there a way I can enable full text search on this existing instance?
We are going to implement a SQL 2000 cluster in an active/passive setup. We are going to use multiple instances. What I am confused about is the naming of the virtual server and instances. In the microsoft documentation it states that all instance/virtual names must be unique across all nodes in the cluster. But the client always specifies the same virtual server name when connecting so how can the names be unique across all nodes??
I would have thought that if there was an instance created called inst1 on node A then during the installation that instance name would be replicated to the failover node B. When installing another instance on Node A do you have to specify a different virtual server and instance name on the failover node B??
Should SQL Server 2000 (Enterprise edition) running on a Win2K Advanced Server (Active / Passive) cluster fail-over seamlessly?
We have been assured by our suppliers that current client connections (ODBC using TCP/IP) cannot be maintained during a fail-over. The result is that during a fail-over the client applications crash and users have to restart.
Do we have to modify the client application so that during a fail-over it will attempt to re-establish a connection?
Pointers to any resources for SQL 2000 clustering would be gratefully received (especially any which support the view that fail-over should be seamless).
I have had questions from management about whether SQL 2000 clustering on windows 2000 is any good.
We are looking at spending *quite* a bit of money to implement it, but I want a "from the trenches" opinion of what its like , from the people that actually use it & look after it.
e.g.
DOES IT WORK LIKE IT SHOULD???????? Is it reliable? Is it resource hungry? Can I trust it to do what its supposed to do?
All repsonses very welcome. No response too small.
I have an existing, licensed installation of SQL 2008 R2, with one database instance. I need to add a second instance, but do not currently have access to the installation media. Can I use the Microsoft® SQL Server® 2008 Enterprise
Evaluation: Trial Experience for IT Professionals installer that's available for download from the Microsoft download site?
Hello, Can anyone give me a site that shows Clustering on SQL Server 2000 step by step. I am trying to have two or more servers acting as one and to get high-availability without having any impact on the application side.
Environment: SQL Server 2000 SP3a on W2K Advanced Server SP4. 1 IBM Server x440 with FastT700 Storage (Fibre Channel)
We need to buy another IBM Server x440 or x445 and we would like to make a cluster. Question 1: Once we build the Cluster with the installation of the Cluster Service, making the W2K Cluster, is it possible to upgrade the default instance of SQL Server to a default clusterd instance of SQL Server? In BOL I have found a note that explain how to do this but I have some doubts.
When I installed SQL Server I placed the system files on the C: drive, the DB files on our SAN on disk E: and the log files on disk F:.
Question 2: If we would like to use Windows Server 2003 what would be the possibility for an upgrade? I mean, should I erase all and start with Windows Server 2003 setup or can you suggest to upgrade the OS first, from W2K Advanced Server, and then cluster SQL Server if possible?
Can you advice please? Any help is really appreciated. Thank you very much for your time. Franco
Are there any decent articles,troubleshooting guides,monitoring guides, books out there, which provide information on setting up SQL 2000 on Windows 2000 using clustering.
I have 2 Node Cluster with 2000 Advanced. I have SQL 2000 Enterprise. I am trying to setup a failover cluster (active/passive)
I have tried to follow the Microsoft Documentation that came with the box but whe hey what do u know - cannot get it to work. I cannot understand the lines "install a default instance of SQL that runs on both". What does this mean?? I know what a default instance means but running on Both ???
Does anyone have document that will show me the steps.
If we have a stateful connection (RDS) and the database fails how will the application reconnect. I do not believe that our application was written using MSCS API. Therefore I don't believe that it caches the user logon and password to log back into the session. So, my question is can the application work with sql server clustering since it uses stateful connections? Any help would be greatly appreciated. Thanks
If I install a new named instance of SQL Server 2008 R2 on a machine that already has 3 named instances that are upgraded to service pack 3, will the install of the new instance overwrite any of the current SP3 files? Will I have to re-apply SP 3 to the existing instances?
Does anyone have any information or know where I can get information about setting up SQL2000 and Windows2000 clustering? We want to set up 3 SQL 2000 servers on Windows2000 clustering. We cannot find any technical documentation about the 2 together. If you know of any books or sites please let me know.
Is SQL 2000 clustering on windows 2000 any good ??
We are looking at spending *quite* a bit of money to implement it, but I need opinions of what its like from the people that actually use it & look after it.
e.g.
DOES IT WORK LIKE IT SHOULD???????? Is it reliable? Is it resource hungry? Are there lots of bugs?
All repsonses very welcome. No response too small.
I am getting ready to have a SQL Server failover cluster setup. I have used SQL 2000 for years, mostly for DTS and related database activities, but NOT in a cluster. I have used SQL 2005 for about one year but not intensively, and NOT in a cluster.
We need to set up a cluster. We are setting up a DELL EMC solution. I am going to hire a consultant to set it up, including the SQL part. My questions are should I use SQL 2000 or 2005? (I don't know if one is better than the other for clustering. Both are supported by our vendor for the application we are running.) How hard is it to maintain a cluster if one hasn't had experience in that area before? How should I prepare?
Any opinions or experiences that you would like to share would be helpful.
The box I am trying to connect to is running two instances of SQL Server. There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'. I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" /> However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried: <add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" /> but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used: <add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" /> but this doesn't work either.
Am I mssing something here? Any help much appreciated Thanks...
I recently had to reinstall a new instance of SQLServer 2000, but was unable to use the previous server name. As a result, my Access2000 front end is not happy with it's linked tables. I can't seem to find anyplace within Access to universally change the address of the SQLServer used as the back-end for all linked tables.
When I do try to access the linked tables through Access, I get an error, and the option to change the server location. When I try to type-in the new SQLServer location, there is an attempt to reconnect to SQLServer, but a whole lot of errors are generated, and none of the data is transferred into the Access table.
I really don't want to have to re-do my Access front end, so it seems it would be easiest to somehow reinstall SQLServer to have the same server location it used to. Is there a good way to completely erase all traces of SQLServer so that I can have better luck reinstalling it to the same location it used to be in? Just using the uninstall program from SQLServer doesn't seem to be cutting it.
We have 2 env. : Testing and Production, both are running Windows 2003 Enterprise Server with SQL Server 2005. The difference is Testing is NOT running Windows cluster but Production do so, what is the best way to transfer a database from testing to production?
We have another systems that both testing and production are running on NON-cluster and we use backup/restore to transfer the database, can it apply in this case.
And I found that there are a tools called DTC, which can transfer all DB objects from one DB to another, is it a best way to transfer between non-cluster and cluster env.?
We would like to install Sql 2005 Enterprise Edition (including database engine, reporting service, integration service and analysis service) as a sepearte instance on a server which already has Sql 2000 with reporting services and analysis services. We do not want to disturb the existing sql 2000 setup.
If we do that then what will happen to my earlier sql 2000 reporting service? Will it be upgraded to sql 2005 reporting service? I heard that reporting services are instance unaware application. Where will be the default reporting service database available?
I started with a SQL 7.0 installation and installed an instance of SQL 2000. The default instance is SQL 7.0 as expected and both run fine. However, now I'd like to upgrade the SQL 7.0 instance to SQL 2000, but the setup procedure on the install CD only allows you to upgrade/modify the SQL 2000 instance. It seems as though once you've chosen to install SQL 2000 as an instance, you do not have the opportunity again to upgrade the SQL 7.0 instance in place. I tried to remove the SQL 2000 instance and reinstall 2000, but the procedure does not give you the opportunity to upgrade the SQL 7.0 instance -- only to modify the programs installed. Any suggestions?
(I could use the Copy Database Wizard to move all databases along with associated stored procedures, logins, etc., but then I'd have to mess with DTS packages, etc.)
I cannot register, from my W98 workstation, an instance of SQL 2000. I just installed SQL2000 (evaluation edition) on my server. Previous to my install I had MSDE installed on the server and successfully registered it from my W98 workstation. When I installed the SQL2000 it recognized there was already a version of SQL Server (MSDE) on the server and said that was the default. Hense, I installed the SQL 2000 as an instance using the format servernameinstance. I can see both of them on the server EM with no problem--I just can't register the SQL 2000 instance from my workstation. When asked for the server name I use the format servernameinstance as it appears in the EM on the server. However, I get the error that the server does not exist or access is denied.? What could I be overlooking? Any help would be much appreciated.