Showing posts with label sp1. Show all posts
Showing posts with label sp1. Show all posts

Wednesday, March 7, 2012

Is it a bug?

Hi,

I'm running SQL 2K5 with SP1.

Whenever I try to run an import from Oracle linked server to my sql server (of course, there are no problems with the import), and if I try to expand any of the folders like Tables, Programmability -> Stored procedures, functions...............I'm not able to see any tables and SPs etc.

It times out and displays error message "Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222).

The linked server (Oracle) import takes 30 to 40 mins and each time it only touches a single table and I don't think this should cause that kind of error but it is.

I'm running this import from Management Studio.

Anybody has any thoughts?

Thanks,

Siva.

SQL Server Management Studio needs some locks to provide the listings. Certain types of data import processes can block other access to the database.

If you can use another method to import data that doesn't lock so much, you can eliminate this problem. I don't know any specific solutions, unfortunately.

-Ryan / Kardax

|||

Hi Ryan,

Thanks for the info.

I did couple of tests on this. It looks like this problem is happening only when importing data but not when querying the linked server inspite of querying also takes lot of time.

Then I tried this import using SSIS and I'm not getting those problems mentioned earlier.

But to be frank, getting data from linked server is very straight forward (when you don't have to do any manipulations with data) and easy compared to SSIS (in my case).

Hopefully, Microsoft will look into this.

Thanks,
Siva.

|||Yes, but linked servers were primarily designed to allow you to offload a query to a remote destination, have it execute it, and then get the results back. It wasn't designed as a data import mechanism. SSIS was designed as a data import mechanism so it is optimized for that type of activity with as low of an overhead as possible.

Friday, February 24, 2012

IS install after SP1 fails

Subject says it all; I need to install IS, but the installer says v.2047 of IS is already installed; it it NOT installed. When I go to add/remove programs, under the Sql Server 2005, it allows me to try to install IS, but that also fails, as no components are found for installation. This is SS dev edition, W2003.

I can uninstall SS2005 and start over, but is there a quicker way to fix this?

I don't think this is a known issue. If time to solution is your top priority, probably uninstall/reinstall is the way to go. Otherwise, post links to both the RTM Setup logfiles (%Program Files%\Microsoft SQL Server\90\Setup Bootstrap\Files) and the SP1 Setup logfiles (%Windir%\Hotfix) and we'll see if we can't help you figure out what's going on here.

Paul

|||

I'm kind of curious; I'm not sure which log files you need (and they are too large to post?). The hotfix.log is from April (sp1), and here is a snip:

04/25/2006 08:10:44.168 Found Report Server 2005 product definition
04/25/2006 08:10:45.371 Found DTS 2005 product definition
04/25/2006 08:10:46.871 Determining QFE level for product instance
04/25/2006 08:10:46.917 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\DTS\\Binn\DTSPipeline.dll
04/25/2006 08:10:46.933 Found following QFE level for product instance : 1399
04/25/2006 08:10:46.933 Determining GDR branching Hotfix for product instance
04/25/2006 08:10:46.949 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\DTS\\Binn\DTSPipeline.dll
04/25/2006 08:10:46.964 No GDR branch Hotfix found for product instance
04/25/2006 08:10:46.996 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
04/25/2006 08:10:47.011 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
04/25/2006 08:10:47.027 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
04/25/2006 08:10:47.042 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
04/25/2006 08:10:47.105 Attempting to check IA 64 platform
04/25/2006 08:10:47.121 Result of IA64 check: 0
04/25/2006 08:10:47.136 Last error: 0

And there is a good logn sqlsetyp0006_qsqlca1_support.log, note the line that says:


MSI (s) (0C:60) [07:14:04:228]: File: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Microsoft.SqlServer.DTS.UpgradeAdvisor.dll; Won't Overwrite; Won't patch; Existing file is of an equal version

logging stopped: 6/16/2006 7:14:06 ===

|||

Yes, the logs will be too big to post here. Instead, you'll need to post a link to the files.

I think this is your scenario; please correct me if I'm wrong:

1. You installed RTM, but didn't include IS in the install. [Log files for the original install will be in the %Program Files%\Microsoft SQL Server\... location]

2. You installed SP1 [Log files will be in the %Windir%\Hotfix location]

3. You attempted to add IS to the product by going to Add/Remove Programs (ARP) and selecting "Change" for the SQL Server 2005 entry. [Log files will also be in the %Program Files%\Microsoft SQL Server\... location]

Does this make sense?

|||

1. yes

2. yes

3. yes, after install of IS from media failed.

'post a link'....sorry, I don't get how to allow you to securely access an internal server?

Monday, February 20, 2012

Is bug 351711 fixed in MSDE 2000 SP1 or later?

I'm reading this article http://support.microsoft.com/?id=285100. I wonder
whether it is fixed or not in MSDE 2000 installation. If yes, fixed in which
SP?
The hot fix is released JAN-22-2001 and the article is Last Review : October
7, 2005. The article does not mention anything about whether the hot fix is
included in SP and it does not mention which SP does this bug applies to. By
reading the article, I will assume this only applies to MSDE 2000 without SP
and fixed in SP1. But can I assume that?Just download the latest MSDE version (Microsoft SQL Server 2000 Service Pack
4
http://www.microsoft.com/downloads/details.aspx?familyid=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&displaylang=en
or directly from
http://www.microsoft.com/downloads/info.aspx?na=46&p=6&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f1%2fb%2fd%2f1bdf5b78-584e-4de0-b36f-c44e06b0d2a3%2fSQL2000.MSDE-KB884525-SP4-x86-ENU.EXE&oRef=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdetails.aspx%3fFamilyId%3d413744D1-A0BC-479F-BAFA-E4B278EB9147%26displaylang%3den
"Peter" wrote:
> I'm reading this article http://support.microsoft.com/?id=285100. I wonder
> whether it is fixed or not in MSDE 2000 installation. If yes, fixed in which
> SP?
> The hot fix is released JAN-22-2001 and the article is Last Review : October
> 7, 2005. The article does not mention anything about whether the hot fix is
> included in SP and it does not mention which SP does this bug applies to. By
> reading the article, I will assume this only applies to MSDE 2000 without SP
> and fixed in SP1. But can I assume that?

Is bug 351711 fixed in MSDE 2000 SP1 or later?

I'm reading this article http://support.microsoft.com/?id=285100. I wonder
whether it is fixed or not in MSDE 2000 installation. If yes, fixed in whic
h
SP?
The hot fix is released JAN-22-2001 and the article is Last Review : October
7, 2005. The article does not mention anything about whether the hot fix i
s
included in SP and it does not mention which SP does this bug applies to. By
reading the article, I will assume this only applies to MSDE 2000 without SP
and fixed in SP1. But can I assume that?Just download the latest MSDE version (Microsoft SQL Server 2000 Service Pac
k
4)
http://www.microsoft.com/downloads/...&displaylang=en
or directly from:
http://www.microsoft.com/downloads/...r />
.MSDE-KB8
84525-SP4-x86-ENU.EXE&oRef=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdeta
ils.aspx%3fFamilyId%3d413744D1-A0BC-479F-BAFA-E4B278EB9147%26displaylang%3de
n
"Peter" wrote:

> I'm reading this article http://support.microsoft.com/?id=285100. I wonde
r
> whether it is fixed or not in MSDE 2000 installation. If yes, fixed in wh
ich
> SP?
> The hot fix is released JAN-22-2001 and the article is Last Review : Octob
er
> 7, 2005. The article does not mention anything about whether the hot fix
is
> included in SP and it does not mention which SP does this bug applies to.
By
> reading the article, I will assume this only applies to MSDE 2000 without
SP
> and fixed in SP1. But can I assume that?