September 24, 2008 at 8:54 am
Hi guys,
I have never applied patches over my SQL Server 2005 databases, and I think I am in need of that....but honestly I don't know how to do it. Would somebody can help me giving me some hints, so I will know how to go to start working on this.
Thank you so much.
September 24, 2008 at 1:51 pm
I would install the service packs on a QA or Dev box before doing it on production.
First you need to find out what build you currently have. It is listed in object explorer window next to the server name i.e. 9.0.2047 is sp1
If you have Service Pack 1 already installed you can then get service pack 2
http://support.microsoft.com/kb/921896
Then you can get the cumulative hotfixes for service pack 2. I think it is up to cumulative 8.
http://support.microsoft.com/kb/951217/
Microsoft will email you the install files.
hope this helps!
September 25, 2008 at 12:10 am
CU9 is already available and according to Microsoft, CU10 is currently build :hehe:
Vote for SP3! 🙂
Tip: to check if your SQL is up-to-date: http://support.microsoft.com/kb/937137
Wilfred
The best things in life are the simple things
September 28, 2008 at 5:06 pm
Hi Guys,
This is getting me crazy...please I need a little more help..I sent an email with the request, but I also want to check myself the downloads I need, due to I have 8 SQL Servers, but I went to "The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released" link.....and nothing show up...just a big list, but where are the patches, where I can download them from??....:crying:
I have been spent almost more than 4 hours trying to find a link to get me to the patch...
I am Oracle user...and I started using Microsoft due to I find it more "friendlier" than Oracle, but this is a mess..
Any help?
Thank you.
September 29, 2008 at 2:39 am
As mentioned above test all patches on a dev/test environment first before applying to production systems.
I would recommend applying SP2 but unless your experiencing specific problems that a later cumulative update fixes I wouldn't necessarily apply them. The url below also provides microsoft kb article links which should point you to the downloads.
SQL 2005 Build List including cumulative update v9
http://www.sqlservercentral.com/articles/Administration/2960
I also believe SP3 is scheduled to be released, although I don't believe there is an official release date yet!
September 30, 2008 at 11:17 am
If you are at or planning on going to SP2 (which is highly recommended) there is a security patch that has been released to go on top of SP2. Here is the link:
October 1, 2008 at 3:05 am
If your main experience is with Oracle, I thought you might welcome a summary of how MS support SQL Server.
While Microsoft are developing a product, they will often release specific builds of the product, often called 'Community Technology Preview' or CTP.
When the product is deemed ready to go live, MS release a given build in a process called 'Release to Manufacturing'. You will often see discussions referring to the RTM version. For SQL Server 2005, the RTM build is 1399.
Every now and again, Microsoft release a Service Pack for SQL Server. There is no fixed schedule for these. A given SP includes a rollup of all previous fixes. Therefore if you are using SQL Server 2005 RTM and want to get to SP2 fix level, you just have to apply SP2. Finding the right place to download a SP is not always easy, but Googling 'SQL Server 2005 SP2 download' normally finds the site. Most SPs for most products can be freely downloaded, but for some products (not SQL Server) you need to register (for free) to get to the download. A SP is rigorously tested by Microsoft before release, so it should not contain any serious bugs. However, both SP1 and SP2 for SQL Server 2005 did contain pervasive bugs and you are recommended to apply at least the first Cumulative Update for each of these SPs. The build level of SQL Server 2005 SP2 is 3042.
For SQL Server 2005 and SQL Server 2008, Microsoft are issuing 'Cumulative Updates' about every 2 months. A given CU relates to a specific SP, and contains a rollup of all fixes released since the SP. Microsoft article KB937137 lists all fixes and CUs issued since SP2. To get to the download page for a CU, either Google for it (SQL Server 2005 CU9 download) or go to KB937137 and click on the links on that page. To do the download of each CU you must register with Microsoft. They will then email you the download details. The file you download is a password protected executable, and you need to run it before the password expires. Running this file will give you a new executable which is the actual CU install. The CU install is not password protected and can be run at any time. A CU is not tested in as much depth as a SP, so some people are wary of installing CUs. Other people will regularly update their servers maybe 2 or 3 times per year to either the latest CU or latest but 1 CU. Even if you do not want to normally use a CU, you should install at least CU1 as it fixed a number of serious issues introduced by the SP. The latest CU is CU9 for SP2, which is build level 3282.
Microsoft also issue Hotfixes for each problem they fix. A Hotfix is always at a given build level, and contains a rollup of all fixes released since the last SP. Hotfixes get the least testing, and you should normally only install a hotfix if you hit the specific problem. Even if you do hit the problem, many people prefer to wait until the next CU is issued.
Inside Microsoft, the same teams are responsible for developing new versions of SQL Server and fixing existing versions. This is part of the reason why SPs are few and far between. However, the SQL Server authors are more responsive to customers than some other MS authors, which is why we get the two-monthly CU releases.
If you want to suggest a new feature for SQL Server, you have to use Microsoft Connect. Google knows the address for this site, and you will have to register to use it. One item currently on Connect is a request for MS to create SP3 for SQL Server 2005. If enough people vote for this, it should happen.
Finally, if you need to contact Microst support, they are called 'Product Support Service', and you will simetimes see discussions that refer to PSS.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 1, 2008 at 3:32 am
One item currently on Connect is a request for MS to create SP3 for SQL Server 2005. If enough people vote for this, it should happen.
I was under the impression it was going to be released before the end of the year?
http://blogs.technet.com/dataplatforminsider/archive/2008/04/15/sql-server-2005-sp3-coming-soon.aspx
http://blogs.msdn.com/psssql/archive/2008/04/25/sql-server-2005-sp3-and-self-service-hotfixes.aspx
October 1, 2008 at 8:23 am
Here is the link to download sp2
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply