Service Pack Install Causes Insert...into Or Select Into To Take Hours
Jan 3, 2000
Hi!
I am totally new to this but have access to a SQL Server (version 6.5) and am looking at the processes used on it to learn. It is being used as a reporting server and have run into a wierd problem:
We discovered that it did not have any service packs at all on it so we applied SP4 to it (Microsoft SQL Server 6.50 - 6.50.281 (Intel X86) ).
Now what took a few minutes takes **hours** to do. In particular, a particular SELECT INTO statement that has a few joins in the WHERE clause is the problem. I changed the code from the SELECT INTO and created the table and used an INSERT...INTO statement. This did not help.
This process has ran successfully on the SQL Server without any service packes for over two years and now with the SP4 applied, it takes forever.
The SQL statement that is used has also been working fine for the same amount of time. One thing that I notice with it is that the join syntax uses *= instead of the more current way (LEFT OUTER JOIN). We are also clearing the logs before running the statement to make sure the space is available. This is run against a header table with around 600,000 rows and a detail table with approx 1,500,000 rows.
I am new to Visual Studio (Pro Edition) and to SQL 2005. I installed the VS Pro, on Vista Business edition. Now I'm wondering if I need to install SQL-SP1 and SQL-SP2. Or do I install just SQL-SP2. Also which version of SQL-2005 is installed with Visual Studio? Standard, Express?
I would like to thank anyone in advance for your time to answer my question.
We are running SQL Server 7.0 on an NT Server in an NT environment. We have Service Pack 2 installed on the server hosting the database. Do we need the service pack installed on the client machines? Even if they only need client connectivity? Also does anyone know what fixes sp3 is supposed to fix? We are running our production environment without any known problems using sp2 and really dont want to disrupt it with sp3 if its not needed. Thanks in advance.
Has anyone had a problem when installing service pack 2 or 3 on SQL Server 7.0? I'm stuck at MDAC upgrade every time, had to 'end task'. Did select @@version afterwards, still on the old version. I didn't try service pack 1 yet.
I found the following page titled "Can't install SQL server service pack 1", but I'm unable to access. http://www.swynk.com/archive3/4500/45001235457.asp
Any help will be appreciated. Please email me directly. Thanks in advance.
Hi, i have a clean install of VB2005 Express and it's accompanying SQL Server 2005 Express (yes i'm new to .net).
After installation i ran Windows Update and it found about 40mb of updates including SP1 for SQL Server. All installed correctly up to a reboot point, after which it continued with the update process.
When it reached SP2 (for SQL Server) it tried to install but just says "Updates were unable to be successfully installed" and "The following updates were not installed: Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896)".
Now i have a permanent icon in my system tray which when clicked tries to do the install with the same result.
During the attempted install my floppy drive 'buzzes' a couple of times.
I'm running an AMD3000+ (64bit) cpu with Windows 2000 Pro SP4
As mentioned in another post (on the VB Install forum) my MyDocuments folder is on a networked pc which has caused other non related problems, not sure if this could be responsible for the error. It would seem unlikely as SQL SP1 installed without any errors.
I am a member of the Administrators group, and there is plenty of space in all hard drives, plus the temp directory is open for "everybody" to full-control it. Yet the Service Pack 2 database engine fails, all other components upgrade fine.
---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 3033 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29506 Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user SYSTEM. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive. -
We are having trouble installing SQL2000 service pack 4 on our server. The package runs through and looks like it installs files to c:, but the install never asks us for any of the questions regarding the install of service pack 4. One issue we were thinking about was that MSDE was installed on the server also. We have a 2003 server with SQL 2000 sp3 (8.00.760)
Hi dear Devs! I have a problem and now I am not sure, what I should do. "Microsoft Update" Service warned me, that a new critical update is ready for download. It was the update "SQL Server 2005 Express Edition Service Pack 2", I did that. Untill here no problem. The update "SQL Server 2005 Service Pack 2" was ready for download too. I have both versions on my computer "SQL Server 2005 Express Edition" and "SQL Server 2005 Developer Edition". The Express Edition came together with the install of "Visual Studio 2005 Team Suite", two days later I have installed the "SQL Server 2005 Developer Edition". Now to my problem, the "SQL Server 2005 Service Pack 2" installation failed in one point, the name of it is "Microsoft SQL Server Native Client". The whole installation was not interrupted, it told me only at end of this updating that this point wasn't successful - I saw it in the "Summary.txt". While the install I saw that this "Microsoft SQL Server Native Client" was twice in the list of the Service Pack 2 Update. Both of these points had the identical name. In short words, I saw that the SP2 wanted made an update at "Microsoft SQL Server Native Client" twice. I thought, it is because these two editions of "SQL Server 2005" on my computer. But the result is, that the SP2 couldn't update the second 'Native Client'. I checked it in the 'Software' section in 'Control Panel' and I have really two installations of this "Microsoft SQL Server Native Client". My question is, is that normal, is that because I have two "SQL Server 2005" Editions on my computer? And what can I do with this failed part of the SP2. Can someone help me with this failed 'Native Client' SP2 update? I were really happy, if someone could give me the best solution to fix this problem. Thank you very much for your help and answers
I'm trying to install Service Pack 4 to our default instance of SQL Server 2000 with SP3a, on a Windows 2003 Server, which also has a named instance of SQL Server 2005 on it and a named instance of SQL Server 2000 with SP4.
The installation appears to be running just fine, but MUCH too quickly. The last window appears stating something along the lines of 'Updating Active X components'. I'm expecting the scripts to run to update my system stored procedures, etc., but that never occurs. The installer just quits.
No errors in the Windows logs, nor in SQL, and no C:WindowsSQLSP.log file.
I tried the installation again, but this time used a different copy of the service pack 4 installer, with the same results, and again no SQLSP.log file.
Since I was going to remove the named instance of SQL Server 2000 anyway, I verified that my SP4 installer was good by uninstalling the named instance of SQL Server (the one with SP4 already), reinstalling a named instance of SQL Server 2000, and reapplying SP4 to this named instance. Everything went flawlessly.
I then tried reapplying SP4 to the default instance of SQL Server 2000, and this time a SQLSP.log file was finally generated. In the error log, the last entries are:
19:10:03 C:PROGRA~1COMMON~1MICROS~1SQLDEB~1SQLDBR~1.EXE sqldbreg2.exe -RegServer 19:10:04 An error occurred while setting the registry value for: SoftwareMicrosoftMSSQLServerMSSQLServer 19:10:04 Could not restore AuditLevel registry key 19:10:04 Action CleanUpInstall: 19:10:04 Installation Failed.
I confirmed that the service accounts that are running SQL Server both have local administrative access to the server (which may or may not matter), and that they are both sysadmin, so I don't think it's a permissions issue to the registry. I've also verified that the account I was using to run the SP installation also has local admin access on that box.
So, I compared my HKLMSoftwareMicrosoftMSSQLServerMSSQLServer registry entry from our production server to the one on the test server, I see that our test server's entry is completely empty. On production there are numerous subkeys, such as CurrentVersion and RPCNetLib.
I'm planning on copying the registry entries from production to test. Should this be sufficient, or are there other things I should look out for?
I am attempting to install SQL Server 2005 Developer Edition (from CD) on my IBM PC with XP Operating System. During set up, I get a error message (see below) telling me about a Service Pack requirement. When I click on the link provided in the error message, it does not lead to any service pack download.
I'm trying to read thru these forum posts, it seems that there is a service pack that I need to download after installing SQL Server 2005. But how can I install the pack after when I can't install SQL Server. Any help would be greatly appreciated. Below is more information about the version of windows my PC has.
My PC: Windows Version 5.1 (Build 2600.xpsp2.030422-1633:Service Pack 1)
Error message from install program:
Operating System Service Pack Level Requirement. (Error) Messages Operating System Service Pack Level Requirement.
"The current operating system does not meet Service Pack level requirements for this SQL Server release. Install the most recent Service Pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again."
I have Windows XP Professional Version 2002 Service Pack2.
I Have:
Microsoft SQL Server Management Studio 9.00.2047.00 Microsoft Analysis Services Client Tools 2005.090.2047.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158) Microsoft MSXML 2.6 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.5730.11 Microsoft .NET Framework 2.0.50727.42 Operating System 5.1.2600
Service Pack is failing to Install CLIENT COMPONENTS; message is:
Product : Client Components Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log Error Number : 29549 Error Description : MSP Error: 29549 Failed to install and configure assemblies c:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
This situation, I am guessing, also preventing me to run import/export from the SQLServer Client.
I am continually prompted to download & install this SP by the windows update utility but it always fails to install it. I have XP SP2. No error msg is provided. I do not have ACT! installed. I do have Oracle 10g Expr. Ed installed. Competitive jealousy?
I found this online:
Important notes about the cumulative hotfix package €¢ You must enable the SQL Server Management Object (SMO) extended stored procedures and the SQL Server Distributed Management Object (SQL-DMO) extended stored procedures before you install the cumulative hotfix package.
Where does one enable SMO & SQL-DMO?
I looked in the summary log file in the Hotfix directory and it says that the problem is that SQL Express cant be started. See below.
I went into the SQL Configuration Mgr and tried to start it and it fails to start. No reason given. Now what?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Time: 11/22/2007 09:44:37.546 KB Number: KB921896 Machine: TOSHIBA-ROGER OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: /quiet /allinstances Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Express Database Services (SQLEXPRESS) ENU RTM 2005.090.1399.00 x86 EXPRESS Express Database Services (SQLExpress) ENU RTM x86 EXPRESS
********************************************************************************** Products Disqualified & Reason Product Reason Express Database Services (SQLEXPRESS) Unable to start service
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : Express Database Services (SQLEXPRESS) Product Version (Previous): 1399 Product Version (Final) : Status : Not Applied Log File : SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools Error Number : 11042 Error Description : Unable to start service ---------------------------------------------------------------------------------- Product : Express Database Services (SQLExpress) Product Version (Previous): Product Version (Final) : Status : Not Applied Log File : SQL Express Features : Client_Components,Connectivity,SDK Error Number : 0 Error Description : ----------------------------------------------------------------------------------
********************************************************************************** Summary Unable to start service Exit Code Returned: 11042 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
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?
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : Express Database Services (SQLEXPRESS) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : D:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9Express_Hotfix_KB921896_SQLEXPR.EXE SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools Error Number : 1332 Error Description : *** Shared String ID 1332 Not Found *** ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 1332
Does Anyone know if there is a way to verify the SQL Service Pack Version on 7.0 on Windows 2000 Advanced server?
I'm getting this results for select @@version
Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) Nov 27 1998 22:20:07 Copyright (c) 1988-1998 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 1)
I installed Service Pack 5 on SQL 7.0 successfully, but when I go back to run @@version, it gives me Service Pack 2 which is the old pack. Does anyone know why and had an experience with this?? Thanks wonderful people!!!
I have a cluster server, with SP3 coming out I wanted to upgrade the SP2 I have right now, when I start SP3 installation it starts and quickly exits from the program. DO I need to uncluster the server before applying SP3? or there is a way arround it?
has anyone had this experience before after we installed service pack 2 our jobs are taking about 10hrs, some run it says it's succesfull but it didn't update the tables.
I have installed service pack-1 on SQL SERVER 7.0 Standard Edition. After the pack is installed @@version is still showing 7.00.623 instead of 7.00.699 HELP !!!
Does anyone else have any concern about this Watson technology creeping in to SQL Server in SP3? I don't like it in Explorer and I'm sure not going to like it in SQL Server!
BTW, Forrest article about the new security patches at http://www.databasejournal.com/news/article.php/1475241 is in error, I think, when it refers to SP4.
Is the sql server 2000 service pack 3 worth applying to production database server or should I still wait. i do have sql 2000 service pack 2 on the server ?
