Himy first post in the data access forums, I really hope, someone can enlighten me here...I have a windows server 2003 running with 15 MSDE instances. No I would like to upgrade to SQL Server 2000 without crashing the existing instances... My perfect scenario woudl be- install sql server as new instance- move existing databases via detach / attach to the new instanceWill that work?
I have installed two mssql 2000 MSDE sp4 instances on WinXP SP2. I can connect both instances from local machine. But when I try from remote PC, I can only connect to one with default instance name and can't connect to another one ComputerNameInstanceName.
I set the windows firewall off in WinXPSP2. But still can't connect.
I also try with mssql2000 MSDE sp3 instances. It is same ask sp4. Please help!!!!!!
Just wondering. On some workstations and a couple of servers we have apps each running an instance of MSDE so these machines each have anywhere between 2 - 5 instances of MSDE each.
Would it be benificial from a resources point of view (not to mention a patching one) if we set up one instance of Express to replace the multiple MSDE ones?
I am trying to upgrade my MSDE 2000 (SP3)to SP4, but it is giving an error of "invalid instance".
Here is what is on the machine (before running any commands):
I do not see any SQL Server installation on my machine under Start-All Programs. But, I have a directory for SQL Server under: C:Program FilesMicrosoft SQL ServerMSSQL
The sqlserver.exe is in C:Program FilesMicrosoft SQL ServerMSSQLBinn and version = 2000.80.760.0
To upgrade MSDE 2000 (SP3) to MSDE SP4, I downloaded this file from Microsoft's website: SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE
I ran the above .exe and extracted the files on my hard drive. Now, I have the C:SQL2KSP4MSDE directory and the Setup.exe is in the MSDE directory.
I looked in the services and stopped the following service: MSSQLSERVER
I tried running: setup /upgradesp sqlrun /L*v C:MSDELog.log This command ran and did not show any error. I then rebooted the machine, checked that the MSSQLSERVER service is running and checked the version of sqlserver.exe but it was still the same (2000.80.760.0). It should have been 8.00.2039
I am not sure what am I missing. All I want to do is update the MSDE Service Pack on our company machines to SP4.
MSI (c) (64:F8) [11:44:29:713]: Grabbed execution mutex. MSI (c) (64:F8) [11:44:29:713]: Cleaning up uninstalled install packages, if any exist MSI (c) (64:F8) [11:44:29:713]: MainEngineThread is returning 1603 === Verbose logging stopped: 08/05/15 11:44:29 ===
the only other error I can see is this:
Action start 11:44:29: RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. MSI (s) (A8:B4) [11:44:29:651]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI19E.tmp, Entrypoint: RestoreSetupParams SOFTWAREMicrosoftMicrosoft SQL Server Setup.{FE7E950B-220A-4182-B5CA-19397244DCFD} Entering Function MyMsiEvaluateCondition MsiEvaluateCondition for SQLMSDEInstalled returned TRUE End Function MyMsiEvaluateCondition Error reading setup parameters Action ended 11:44:29: RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3. Action ended 11:44:29: INSTALL. Return value 3.
SYNTAX Used is : setup.exe /upgradesp sqlrun INSTANCENAME= SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=MyPwd BLANKSAPWD=1 /L*v D:MSDE.log
Please note that I am using BLANKSAPWD=1 because BUILTINAdministrators right is not present, the above syntax is working for one named instance but is failing in second named instance.:eek:
I installed MSDE on a pc with no problems, but now I realise I want to create another instance and set DISABLENETWORKPROTOCOLS=1 so I can use Enterprise Manager over the network from another PC.
If I create another instance of MSDE on the PC, can I remove / uninstall the first instance?
Is it any big deal if I leave the first instance?
and last but not least...
If I create a new instance will it see the database I created on the first instance?
told you so...
Can anyone recomend some good literature to explain about instances please :D
So I installed an instance of SQL for an application (WSUS) and all waswell. Having read in many places that I could install multiple instances ofMSDE on the same box, I started the second install today (Live CommunicationServer). The MSDE install portion of LCS gets almost completed and then itrolls itself back and fails with Event ID: 11708. Now when I go back intothe SQL Server Service Manager it says not connected and there are noServices available in the drop down list, including the one that should bethere for WSUS. Should I just reinstall WSUS again (hopefully I won't haveto reconfigure all of the updated approval/deny settings). Any thoughts onwhy the second instance fails? Thanks in advance.
Does anyone know of a resource that describes the steps to upgrade an instance of MSDE(2000) to SQL 2005 Standard?
We found something on a MS site that indirectly indicated you could upgrade the MSDE to SQL Express and then upgrade Express to the full version of 2005, but that method created quite a bit of problems(System databases), which we were not able to resolve short of uninstalling MSDE and the apps and installing SQL 2005 and re-installing the apps; but I have to believe there is a better way.
I installed SQL 2005 Standard Edition first, then MSDE plus its SP4. Both instances are named (MC05WXPPROSQLMC for 2005 and MC05WXPPROUCTO for MSDE). I inadvertently had not allowed the TCP/IP protocol for MSDE during the installation, so I did it manually later, through SVRNETCN.exe which also ships with SQL 2005.
Now: I CAN connect to the MSDE instance with any SQL2005 tools through shared memory. But I CANNOT connect to it through TCP/IP. I guess that this is because wrong port binding for the SQL2005 instance, MSDE instance and SQL Server Browser, but I'm not sure.
I am creating an install for our product and as part of the changes I am making, I want to upgrade a user's DB engine, if they are still using MSDE 1.0, to SQL Express 2005.
The upgrade path we have chosen is the following.....
MSDE 1.0 --> MSDE 1.0 sp4 --> SQL Express 2005
I believe this should work, yes? Anywho, I am trying to run a "passive" install of SQL Express and I am using the following parameter list:
I am having issues trying to do an in place upgrade of msde 2000 to sql express 2005. When I try to upgrade it bombs when it reaches "Running action to shutdown instance(Run As Normal User)" with the following error: Service 'computername' could not be stopped. Verify that you have sufficient privileges to stop system services. The error code is (16386). I've tried an upgrade on a clean test machine, and it goes through without any problems. I am logged into an account with local admin permissions. If any one has any ideas, they would be appreciated.
I think this is a question for the specialists among us.
Can I use one general reporting server (installed on instance MAINREPORTING) for multiple customers who all have their own sql instance (CUST1, CUST2, CUST3, ..) I would use UserAuthenciation on the reportserver url to display the specific reports customers can use.
Is this possible, and what do i have to take care off concerning installation and/or configuration (especially on the reporting side) ?
i have sql server 2005 express running. during install, i had issues with a system dll that i found answers online and resolved. i am still very green, but i know much more now than i did at the time. i believe that as a result of the partial then failed installs i have multiple instances either fully or partially installed. when i am in the sql server mgmt express environment, it lists two sql engines. i only ever use one, and would like to safely remove the second without damaging or corrupting anything done with the other instance. my reasons for wanting to do this are twofold. first, i would like to free up the drive space taken up by the second instance. (i am a stickler for clean harddrive mgmt and maintenance). second, now that i have used the software and am somewhat more familiar with it, i would consider installing a second, intentional instance so that i may attempt to better customize some of the install-time settings and configurations. can anybody give me any pointers/ guide me in the direction of information on how to SAFELY go about this? thank you in advance for any help.
I created a second SQL2000 instance on a Windows 2000 server. The strange thing is that I can create an ODBC connection to the default instance but cannot for the new named instance. If I try from a client that has SQL installed on it, I can see both instances. Any idea why this is happening?
We're trying to decide if we should use a single large instance of SQL Server or multiple instances on the same server. This is for a dev environment.Have to limit max RAM per instance so no instance grabs it all.There will be I/O contention and CPU contention between instances since the different instances won't coordinate with each other.It limits the available RAM for In-Memory tables..It sets lower limits to the amount of RAM available for any given query, causing artificial "contention" even when there's nothing else running at the time.
According to the Task Manager, on my SBS 2003 Server, I'm running multiple instances of SQL. How do I determine which instance(s) are required to maintain server stability, and which are not. My Server resource use continues to be a perennial problem. Please advise.
Is it possible to have multiple instances attach the same database?
I have a scenario where I want to have on one node, a clustered instance and a non clustered instance and both instances attach the same singular DB on a filer.
at the moment I have the following problem: We have installed a version of the MSDE 2000 Sp3 with our software since 2005. Now we install SQL Server Express 2005 in order to use the latest version and to be compatible with Vista. We have never had any problems with the MSDE, so it was no problem that we installed the german version (by mistake) because there never was any output at installation time. When we now upgrade the existing MSDE installing the new version of our software, there are often problems and there are error messages, unfortunately in german, which cannot be read by most of our international users.
The problem is, that there seems to be no possibility to upgrade the existing (german) MSDE with the english version of SQL Server Express 2005. My question is, if it is possible to upgrade the german MSDE to the english SQL Server 2005 to enable our international users to read the error messages at installation time in english?
If I want to install 2 instances of SQL2000, will it install the SQL2K executable files (inn folder) onto 2 different folders, or all instances in one folder but the databases are in different folders.
Please Help me on this. I installed the two instances SQL on one box. ONe is default instance called ACSQL1(actually machine name) and the other one is called ACSQL1/DEVELOPMENT. THrought the my client site of SQL 2000 I can access both instances. When I try to get connection from VB. I can access the default instance but I can not access the second instance. Any ideas about this??? Qun Lu
I am running SQL 7.0 as the default instance and SQL 2K as a named instance. Each is using a different port....7.0 is using port 1433 and 2K is using 1024. Everything appears to be up and running fine on the server. However, I am not able to access the 2K instance from a client. I have tried to use both TCP IP and named pipes setting them up using the server network utility and the client network utility. No luck anywhere. I continue to get connection errors...check network documentation...
Currently, I am running SQL Server 2000 with the default instance. I know SQL2K can run up to 16 instances simultaneously. I would like to add another instance but am unable to find documentation on how to add it. Books online tells me "about" multiple instances, but not how to set it up. I've obviously missed something somewhere. Can someone please direct me to a document that will help explain "how" to add another instance?
We have a DTS package that is submitted every minute by a SQL Agent job (2000). We see instances where before the first job is completed, the second one starts running.
Has anyone encountered this type of behavior before?
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
Is there any limit on SQL server Multiple Instances? if we require to run 60+ Instances on single machine what will be the minimum hardware requirements.
Has anyone run SQL 2005 Standard Edition, 2 or more instances on one server... where you got the extended memory up to 2.8 GB on EACH instance of SQL Server? I've done the 2.8GB game on boxes with ONE instance, but don't think I tried it on a multi-instance box, to get the 2.8GB RAM each. Thanks, Bruce
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
I need to put sql server 2000 enterprise and sql server 7 on the same box. For multiple instancing is it better to run with Win 2k Pro Server or Advanced Server. Please Elaborate.