July 9, 2008 at 10:39 am
Hello!
I ran across this site and hope you can help. I've searched everywhere and am having a perplexingly difficult time finding an answer to my question.
Normally when you go to add/remove features for any MS product, it detects and shows what has already been installed, and if you deselect those items, they will be removed, and any new items you select will be installed. From what I've read, SQL Server 2005 should behave the same way.
With EVERY SQL Server 2005 installation I've run across, including one just yesterday, you go to add a component like SSIS, and every feature shows up with red X's as if it doesn't detect any installed components. I believe in my first experience about a year ago, some of the previous components were actually removed when I didn't reselect them, or were overwritten or something like that, and it made me real gun-shy of adding components.
Just to clarify the issue, SQL Server 2005 DOES show under Add/Remote Programs, but once you drill down past all the initial preparation steps and get to where you can actually add components like SSIS, everything shows with a red X. My understanding is that components with an X could be uninstalled, which I don't want.
I have a client that I need to simply add SSIS to an existing SQL 2005 Workgroup Edition installation, and also one running SQL 2005 Standard, and I don't want to take any chances that the rest of the product will be uninstalled as everything appears with an X. Can you offer advice, or acknowledge this as a bug, known issue, or even just something that has caused confusion for others?
Either I'm GREATLY misunderstanding the interface, or it's confusing or not well explained (most likely the latter, knowing MS's penchant for change for the sake of change... lol).
Thanks in advance!
July 9, 2008 at 1:25 pm
You may try the following command to see what components are on your server.
%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\ARPWrapper.exe /remove
July 10, 2008 at 7:48 am
Hey, thanks for the reply -- I will do that soon once I'm back onsite. But is this an issue (if it's even a true issue) that anyone else has, too? I have the same thing with ANY SQL 2005 install I do, no matter what the version, so it almost seems by design. I do want to know if this is standard behavior, and more importantly, how I can safely add SSIS without fear of harming my existing installation. Both sites have production databases in use and I don't want to accidentally take them down.
Thanks!
July 14, 2008 at 9:22 am
Bump... LOL! Does anyone have any clue about this? I really appreciate any help that can be offered.
Thanks!
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply