January 21, 2003 at 6:34 am
I just downloaded SP3 for SQL 2000 from the Microsoft site (available at http://www.microsoft.com/sql/downloads/2000/sp3.asp). Does anyone have any good (or bad) experiences to report on the final code? Any gotchas?
January 21, 2003 at 7:42 am
I have done 3 installs and not come across anything. However there is a thread on this site that is discussing having issues with the install. Just make sure you do a full backup before and immediately after the upgrade and anything you encounter will just be trouble and not a disaster.
January 21, 2003 at 8:39 pm
I didn't encounter any major problems, but there were a couple of issues during beta testing. Most seemed to have been present in previous releases, though.
As Antares suggested, backup your databases, etc. Remember, the only way to roll back a service pack in SQL Server (currently) is to uninstall, install the previous service pack and restore the databases.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
January 22, 2003 at 5:02 pm
Is there any input on the "cross database ownership chaining" option. Seems if you use 3 (or 4) part table names that reference tables in a different database than the one connected to, there might be an issue.
January 22, 2003 at 5:19 pm
You should test beforehand to decide if you need or don't. You can however change afterwards if needed.
Do a search in SQL BOL for
"cross database ownership chaining"
and you will turn up a few items on this.
But yes it can be if you are not sure.
January 23, 2003 at 2:50 am
I have come accross an issue with sp3.
When designing a DTS package and creating a transform data task from certain tables (possibly only ones with lots of columns) to a text file, enterprise manager crashes.
We use a lot of DTS packages in our enviroment, so we are delaying deployment of sp3 until this is fixed.
January 23, 2003 at 3:51 am
Ant2001 can you post the table DDL and and idea of the package of a situation where the problem is occurring. I have several packages myself but none fail. I would be curious to test it to see if it can be reroduced.
January 23, 2003 at 5:29 am
This is one of the tables it fails on. I have tried it on a couple of machines here and it crashed both times, but it is fine where only sp2 has been applied.
To recreate the problem, follow the following steps
Create the table ab3.
Go to enterprise manager and create a new DTS package.
Create a new sql server connection in DTS designer pointing to the server and database where the table was created.
Create a new text file (destination) connection.
Create a new transform data task with the sql server as the source connection and the text file as the destination connection.
Go into properties of the transform data task and select ab3 as the table in the source properties.
Click on the destination tab and the table columns come up in a new box. Click on execute and the columns are not populated in the box as they should be.
Clicking on the define columns button then crashes enterprise manager.
CREATE TABLE [ab3] (
[CountryCode] [nvarchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[TransType] [nvarchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[UniqueTransId] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[RelatedTransId] [int] NULL ,
[OrderId] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PayMethodCode] [tinyint] NULL ,
[CustomerId] [nvarchar] (6) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[TransDate] [smalldatetime] NULL ,
[ShipmentLineId] [int] NULL ,
[Store] [smallint] NULL ,
[Description] [nvarchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Sku] [int] NULL ,
[FulfillmentSku] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[CurrencyCode] [nvarchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Qty] [smallint] NULL ,
[Amt] [money] NULL ,
[TaxRate] [real] NULL ,
[SaleNetAmt] [money] NULL ,
[SupplierId] [int] NULL ,
[LineType] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[uom_code] [nvarchar] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[x_status] [int] NOT NULL ,
[x_last_update_date] [datetime] NOT NULL ,
[x_processed_flag] [nvarchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[x_recnum] [int] NULL
) ON [PRIMARY]
GO
January 27, 2003 at 5:24 am
I can't get SP3 off the launch pad.
The SETUP.BAT file refers to \x86\setup\sqlsetup.exe as does the readme file however, I don't get a \setup directory within \x86.
I've tried SQL2KSP3.EXE and SQL2kasp3.exe but no luck.
Does anyone have any suggestions?
January 27, 2003 at 10:14 am
I have fouind that if there is not enough disk space on your c:\ drive then even if you are extracting service packs to another drive they do not successfully extract all the files - but say that they do complete successfully!
January 29, 2003 at 1:59 am
The "not enough space on the C:" drive was absolutely correct.
The extraction process must bounce stuff via the TEMP directory or something.
As soon as I had cleaned up my C:\ drive all went fine.
January 29, 2003 at 4:15 am
It expands in temp then moves file to destination.
January 29, 2003 at 6:04 am
timoteo,
As with Andy's suggestion, I'll be putting together an article on cross-database ownership chains in the very near future. I cover one of the main security concerns in my SP3 article. The three part naming convention isn't affected, but how permissions are checked is.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
January 30, 2003 at 2:29 am
No problems installing SP3. However, after installing, select @@version returns:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 2)
i.e the exe version is correct, but it still says Service Pack 2!!
Right-clicking in EM on the server says SP3,
select SERVERPROPERTY('ProductLevel') returns SP3
A bit confusing as up to now, I've tended to use select @@version.
A contact in Miscrosoft is investigating.
Anybody else seen the same?
January 30, 2003 at 2:35 am
quote:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 2)
SP2 referss to Windows SP2 not SQL SP2
Viewing 15 posts - 1 through 15 (of 54 total)
You must be logged in to reply to this topic. Login to reply