I am attempting to install MS SQL 2000 SP2 on a Windows Server 2003 Enterprise SP1 box. The only installer I can find on the disc is in the MSDE directory and when I run it it immediately gives me this error:
"This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."
I have tried copying the install files to my local hard drive for install, I have checked the version of my Windows Installer (3.1.4000.1840). I have the SP4 updates ready to go once it's installed, but I just cannot get past that point. I know that the same software version has been installed on other Windows 2003 systems, so why would it have a problem on this one machine?
Hey there I am an SQL noob, our bank has no real SQL Admin, we had onw that left but never had a good knowledge transfer. We have 2 SQL servers clustered. IBSQL1 and IBSQL2 they make up cluster IBSQL. We have 2 other servers IBIIS1 ans IBIIS2 and we noticed when installing apps on them that they could not see the database. Yet it can ping IBSQL. The problem is on IBSQL1 and 2 port 1433 is not listening or open. Thus on IBSQL it isn't either of course. I have read of all kinds of people having this issue and most have said you need to manually add a connection string "Provider=sqloledb;Data Source=machineName,1433;Initial Catalog=xx;User ID=xx;Password=xx" Problem is I do not know how to add a connection string.
I need step by step instructions since im new to this. Start/programs/etc..... Apparently it is not enough to open the properties of tcp/ip in the config util and say 1433. You need to reenforce it by adding that string.
As it stands I cannot "telnet ibsql 1433" it tells me to take a hike basically.
So is the connection string the likely cause? or could it be something simpler? Thanks in advance.
I am using Windows 2003 Server English Version. I wanna store the big-5data so I install the sql server 2000 as if i install it in the Windows2000 with Server Collation of the Chinese_Taiwan_Stroke_CL_AS.However, the data are stored into the database server in unicodeinstead of big-5 in that of windows 2000 OS.I would like to ask how i can set so that the Sql Server 2000 can storethe big-5 data
We are migration few database from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server)
Problem :
- The performance difference observer was not much (Just 15-18%)
- The CPU Utilization goes to 100% immediately, when the software login screen appears and it sustains in between 90% to 100%
- Multi-User Access (3 or more concurrent users), the sql performance is tremendously slow.
Steps followed for Migration:
- We have used the backup and restore method to migrate the data from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server).
- We ran the DBCC DBREINDEX for each affected tables
- We executed the sp_updatestats procedure for all the tables
- Upgraded the DB compatibility version to 90
- Installed the SQL 2005 Enterprise Server (64 bit-Itanium Server) Service pack 2.
One thing that we observed, was the memory usage, on SQL 2000 the sqlservr.exe uses around 1.5 GB where as on the SQL 2005 its just 120 MB.
A normal select query on 2000 Server took 11-12 sec, having 10 lac records, and the same query on 2005 took 1 min (3-5 sec CPU process taken by sqlservr and rest by the Sever Management Studio.
The only differance noted was that on 2000 the entire data was displayed at one go where as in 2005 the data was displayed at the 1st sec, and was filling the rest in the buffer, and to finally display entire data it took 1 min.
Also
when we run this query
select * from sys.dm_os_sys_info
one column os_priority_class shows a value = 32 ? what does this means.
In the MSSQLSERVER SERVICES, properties, there is a parameter displaying value
Advanced > Running Under 64 bit OS = No ? what does this means.
Could anyone pls suggest as to how to increase the sqlservr.exe memory area, and also how the enhance the performance.
I have a win2k3 server that i am going to need to upgrade to servicepack 2. It is running sql server 2000(sem reports version 8.0 - ithink that is sql server 2000). It has profiler and query analyzerrunning as well. Are there any caveats i need to be concerned aboutbefore installing win2k3 sp2 on a server with sql server 2000. Thanks
For a SQL/2005 DB Server do I need the /3GB switch or not? I will have IIS running on the server; however, it won't be doing very much as the SQL Database is the main thing:
Windows 2003 R2 Enterprise w/16 GIG RAM 4 CPU (Virtual Machine) SQL/2005 Enterprise Edition
Hardware: Dell Server 8 CPU w/32 GIG RAM running VM ESX V3
I know I need the /PAE switch to utilize Memory over 4 GB - the question is do I need the /3GB switch along with the /PAE switch?
Hi all,I have MSDE installed on an HP server as some of the utilities requireda database. I have also subsequently installed SQL 2000 onto thisserver which is a windows 2003 box. I know it complains at the startof the installation but I was under the impression that it would stillwork ok, especially with SP3 applied.I have tried to apply SP3 but it tells me that it is not a SQL2000instance ad setup will exit?Also I have noticed that in the directory structure it has used thedollar sign i.e. mssql$machinename its the same in Enterprise Manager\machinename$InstanceName. Whats that all about? Its not like that onany other server!My plan is to uninstall sql 2k, uninstall HP apps and MSDE andreinstall SQL 2k. Can anyone explain the above though?ThanksGary
We are planning a SQL Server 2005 install on VMware ESX, as thebackend to a Sharepoint Services 3.0 web front end..Do I gain anything at all by installing SS 2005 on Win2k3 ENTERPRISEas the OS instead of Standard??Thank you, Tom
Hello All and Happy New Year (I believe that is still allowed by the PC police?!)
Has anyone experienced performance problems (i.e. processes taking a lot longer to connect to the database server) after appyling Windows Server 2003 SP2 to a server that was previously running Windows Server 2003 RTM? The version of SQL Server (2000 SP4) has not changed between OS Service Packs.
To set the scene, we upgraded one node of a cluster to Win2K3 SP2 intending to upgrade the other node the following night if no problems were encountered. However, after failing over to the patched node we experienced something akin to a Denial Of Service attack whereby connections were gradually refused until even existing connections were kicked out.
We resolved that issue by disabling the SynAttackProtect Registry key (details http://support.microsoft.com/default.aspx?scid=kb;en-us;899599), but although connections are no longer being refused they are taking a lot longer, e.g. opening a Query Analyzer window now takes several seconds to connect to the database. The actual time taken by the database engine to execute sql queries has not increased, but is perceived by the users as having done so because of the time taken to return results.
I asked our server team to run diagnostics against both nodes and they found no problems and no differences apart from the OS service pack level.
I am about to reopen the case I logged with Microsoft, but thought I'd see if you guys had experienced anything similar.
Microsoft Security Paradigmes are Irritating. I sure they're fine onceyou know what they are, but for the uninitiated it's quitecounterintuitive to work with.I moving an old SQL Server-backend-IIS5/ASP-frontend application toservers with windows 2003 standard edition. One server will run thedatabase the other will run IIS 6.0. Note that i haven't set-up adomain, which i think requires one machine to be domain controllerwhich would decrease performance and stuff. I've simply put them on thesame group.I wan't to restrict access the sql server so only the incommingconnection from the webserver is allowed. I can use either namedpipes(which should be the fastest protocol) or tcpwhich should beslight slower than named pipes) but i seem to have a problem. If I usenamed pipes to connect the IUSR(the user under which IIS is running)must have access-rights to IPC$ share on the sql server. I can't seemto set any access-right directly for IPC$ share, but i can reactivatemy guest user and then it works, everyone can now access the ipc$ shareso it's not really what i'm looking for.I can also connect through TCP( and set up some kind of filter onlyallowing incomming connections on port 1433 from the ip of the webserver.But i don't know how to do this. I've taken a look at the IPSec stuffbut it's all about kerberos authentication and other bull which i don'tthink i need. What i need is simply a ip traffick filter, which doesnothing else but reject incomming connection from all other ip's thanmy webserver.My question is how do I do this? Do i need to have a addtitíon"firewall" service running and if so why, how much extra overhead willthis create for the server. Alternately, is it possible to change theaccess right for the IPC$ share manually?Thanks in advance for any input you might have on this?Regs Jens
I am currently working on with the ASP encryption of my application. I've tried to test the encryption of the connection string using the capicom.dll in my local, and it works successfully. However, I am not quite sure if this will still work after my OS is upgraded to WIN2K3 (my current OS is WINXP). Will this dll component be impacted after the OS Upgrade? or will there be no impact at all?
Any inputs from you guys would be much appreciated.
i am using "sql server 2000 enterprise evaluation edition".i am running windows xp.i want to upgrade to "sql server 2005".so please suggest me a sql 2005 edition which provides functionality similar to sql 2000 enterprise evaluation edition and must be compatible on xp.please reply soon...coz i am working on my project.
Hi there Our ISP hosts our data on SQL Server Enterprise, but I also going to host the databases on my local machine. As it's just local would Standard edition do? If I migrate the databases over, will it work? Thanks in advance.
Is there anything significantly better in Enterprise Manager 2000 vs. the old EM from SQL Server 7.0?
If so I'd be willing to pay the $50 for the SQL Server 2000 Developer Edition to get it... if not it seems dumb to pay for anything when MSDE 2000 is free and I already have the old EM. (Although I have installed MSDE 2000 as a new instance and can't figure out how to get at it via EM.)
I have just discovered something with EM 2000. In the old days (SQL Server 7), you could right click on a table, choose OPEN TABLE -> SELECT ALL ROWS and get a nice little grid with the select results. The same is true in SQL Server 2000. One thing you cannot do is update a value in that result set, which WAS something you could do in SQL Server 7. If you try it in EM 2000, you get the error message "TRANSACTION CANNOT BE STARTED WHILE IN FIREHOSE MODE". ??????? Am I just missing something, or was Microsoft so worked up about putting XML into their product, they overlooked some of the simple things that were really appreciated (and sorely missed). If anyone can provide some insight, it would be appreciated.
Can the SQL 2000 Enterprise Manager be successfully installed and utilised on a pc that currently has SQL 7 and is used to administer other SQL 7 servers? Can the SQL 2000 Enterprise Manager be used to administer SQL 7?
is there any kind of problem if i continue to use "sql server 2000 enterprise evaluation edition"..the evaluation period is for 120 days and my project will complete by that period..shall i continue using that or there are any problems....
I am having trouble with sql server timing out. I have the timeout set to maximum, and the query I am running is pretty simple. The data is about 10+ million lines, but It should not have a problem running queries on this. plus the timeout comes before the expiration of the timeout setting. The strange thing is, is that sometimes it will work if you just keep running the query. Has anyone run into this, and is there a fix? Also, sometimes if i link the table to an mdb and run the query through access, it will pull the results! what is that about?
I have an MSDN License from Microsoft and I am trying to install SQL 2000 enterprise edition to my XP laptop. I get an error stating that SQL is not compatable with this operating system. It is only offering to install the client tools. Can someone give me a heads up here and let me know what is going on, because I know I had this installed before.
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.
Is it possible to connect to a SQL Server 7 remotely from a SQL 2000 Enterprise Manager. I have been given the alias config from my web hosting service but no joy on the connection.
I need to max out on RAM somewhere around 3 to 4 GB and I am using SQL 2000. Standard SQL 2000 RAM is limited to 2 GB. SQL Enterprise 2000 is maxed out around 32GB and it cost is $1K. I need to purchase a Windows based SQL package but I can't find the specs on SQL Standard 2003 (which is ~$700) to compare. What is the Max RAM for SQL Standard 2003? Which is a better purchase relative to RAM? What O/S is recommended as this also limits RAM usage?
I have been using my SQL 2000 Enterprise Manager for many months but it suddenly stopped working. I have uninstalled and reinstalled the software 3 times and it is still not working. When I double click on Enterprise Manager, it doesn't run. Query Analyzer works fine.
I am on Windows XP. No change in system configuration recently or any s/w upgrade, etc.
I hope someone out there can help, cos i really need it. We have a 2 node cluster + SAN that will be used as our SQL 2000 servers. We have setup the cluster ok, and have tested failover with no problems. However, when we try to install SQL 2000, it just hangs. I have copied the enterprise cd to the local drive, and am installing from there. We run the setup.bat, create the Virtual Server, and assign an ip address. At this point, it just hangs. Upon checking the SQLSTP.LOG file, this is the last entry in the log: Begin Action : DialogShowSdDiskGroups
I have found the Microsoft Technet Article 293788, which gives me a possible soloution, but we dont have any Resource Names or Groups that have the same name.
Can someone PLEASE give me an answer on how to fix this, or at least point me in the right direction.
Anywhere I can download sql 2000 server enterprise edition eval? I have a database running 2000 standard, wanted to test on 2000 enterprise to see if increased memory and enterprise edtion will help. With the intro of 2005, I can not find 2000 enterprise eval.
We are running a two-node cluster for SQL Server 2000 Enterprise on Windows Server 2003. Each node has four processors and 4GB RAM. Our application is hosted on a seperate IIS server with 150-200 connections accessing the database via ADO.NET (ASP.NET 1.1). Our processor utilization has been high, averaging around 80% and out context switches/sec counter averages around 15,000. We are not using NT Fibers and our performance seems to be sluggish when the context switches/sec counter is high - over 10,000. In peak periods we se this counter hit 30-50,000. I have read articles that state NT Fibers have better performance in machines with 8 or more processors. Is this something that would also help in a four processor machine? The SQL Server is dedicated to SQL, i.e. there are no other applications running. I am also considering using the "Priority Boost" option... do these options really improve performance? I'm trying to squeeze as much performance out of these machines while waiting for new hardware to arrive. Thanks.
I am currently running SQL Server 2000 Standard on my production system, and I am looking to upgrade the system to Windows 2000 Adv. Server. I would also like to upgrade SQL Server 2000 Standard to SQL Server 2000 Enterprise to utilize more than 2GB of memory. Can anyone tell me what is the best way to upgrade the system, and please provide some feedback on your experiences with the upgrade. Thanks in advance.
