I am having problems getting SQL Server 2005 and Visual Studio 2008 to
coexist on my PC.

If I install VS 2008 first Business Intelligence Development Studio does not
install and I don't get the SSIS templates in VS 2008.

If I install SQL Server 2005 first it no longer works after I install VS 2008.

We have hundreds of legacy DTS jobs to maintain as well so I need to install
the backwards compatibility components.

Does anyone know how I can get it all to work at the same time?
--
Derek

Thank you for your reply. I can get everything except Business Intelligence
Studio working by installing VS 2008 first patching it up to SP1 and then
installing SQL 2005. The problem here is the setup program will not install
VS 2005 components when I have VS 2008 installed. Is it posible to download
the SSIS templates and just use them with VS 2008? If so where can I get them
from?

Installing SQL 2005 first seems to be a non starter. As soon as I install VS
2008 I can't even open Management Studio.
--
Derek


"Rick Byham, (MSFT)" wrote:

Hi Derek,

I had the same problem. Here were my steps to solving the problem. The
solution was:
Step 1 - Install SQL Server 2005
Step 2 - Install SP3 for SQL Server 2005
Step 3 - Reboot
Step 4 - Install Visual Studio 2008 SP1
Step 5 - Reboot
After your reboot you "should" be able to not only get into Management
Studio but also BIDS. Post back and let us know how it goes. If it does
not work I will continue to help you find a solution.

SQL Squirrel
http://www.lockergnome.com/sqlsquirrel/


"Derek" <Derek (AT) discussions (DOT) microsoft.com> wrote

Thank you, I will try it out and let you know how I get on.
--
Derek


"Brett" wrote:

Hello Brett & Derek,

I have similar problem: I bought VS 2008 Pro-academic which ships with
SS2005, because I need to find job and they all ask for ssis, ssas, ssrs, so..

I install both, get up to vs 2008 sp1 and ssvr 2005 sp3 (2-day headache
with BSOD til fix 184176) , but no BIDS - SSIS (haven't tried SSAS, SSRS).

Also, SSrver installed but had not icon for SS BI on start menu,
properties said it needed devenv.exe but couldn't find it, so I pointed it to
VS 2008 devenv.exe. I know now it was looking for devenv.exe of VS 2005,
which I don't have.

What do I need to do to install ss2005 BIDS so I can master SSIS without
buying/installing (or at least buying) VS 2005 (which school bookstore no
longer carries) ?

I also need vs2008 to learn latest .NET.

Thanks
Jeff



"Brett" wrote:

The release notes
http://download.microsoft.com/downlo...leaseNotes.htm
has a section about VS 2008. See the part in the middle where is says
Required Actions. Mostly it says to get Visual Studio 2008 SP1.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jeff_B" <Jeff_B (AT) discussions (DOT) microsoft.com> wrote

Hi Rick,

Thanks for quick reply.. but, your link is for SS 2008 and VS 2008.
Are you sayind this applies to SS2005/VS2008 as well ?

If yes, I'll uninstall both, since my first steps had been VS2008,
SS2005, VS2008-SP1, ss2005-SP3. On reinstall, I'll do vs2008, vs2008-sp1,
ss2005, ss2005-sp3.

--Jeff_B




"Rick Byham, (MSFT)" wrote:

Hi Rick,

To be clear, I'm waiting for your confirmation, since I have found other
posts that say VS 2008 does not suppport SSIS for SS 2005.

Is there an alternative fix that will implement BIDS for SS 2005, like
a stand alone hotfix for SS2005/VS2008 customers like me or a developer
version of VS2005 ?

"Jeff_B" wrote:

When I installed SQL 2005's SSIS, it automatically installed a standalone
version of VS2005. I believe VS 2008 was already on my computer, but I'm not
positive which was installed first. I think it was VS2008, because I was
hoping BIDS would use that rather than installing VS2005. I don't remember
doing anything special to get them both working. If it matters, I'm using
SQL 2005 64-bit on Vista 64-bit.

Getting DTS editing to work correctly in SQL 2005 x64 was more complicated,
but I think SSIS worked without issues. Here was info from an old post:

There were some error messages the first time I
edited an existing package. Some of the icons were invisible, but passing
the mouse over them, or clicking to select them, made most of them visible.
After I had saved the packages once, the icons stayed visible and the error
message did not recurr.

The error was "SQL Server 2000 DTS Designer components are required to edit
DTS packages. Install the special web download 'SQL Server 2000 DTS Designer
Components' to use this feature". I said ok to that error and was then able
to edit the package. I
could see the connecting lines, but not the nodes. Sometimes when I just
passed the mouse over a node, or clicked on it, the icon would appear. After
editing and saving the package the first time, it looked, worked and edited
fine after that. This was a very simple package so I could tell what was
where just by guessing.

Here's a post from Mark Han, a SQL engineer, which might help:
"In order to resolve the issue, I would like to explain the following:
A) SQL Server 2008 does not include support for the following DTS features:
1 There is no 64-bit design-time or run-time support for DTS packages.
On a 64-bit computer, DTS packages, and
Integration Services packages that run DTS packages, can run only
in 32-bit mode. To run DTS packages in 32-bit
mode, you have to install and use the 32-bit version of the dtexec
utility (dtexec.exe). To install the 32-bit version of the
dtexec utility, select Client Tools or Business Intelligence
Development Studio during setup.

B) To install the 32-bit version of the Integration Services runtime and
command prompt utilities on a 64-bit x86 computer
During Setup, select Business Intelligence Development Studio or Management
Tools - Complete. Selecting either of these options installs the 32-bit
version of of the Integration Services runtime, the dtexec utility
(dtexec.exe), and other Integration Services tools. There is an article to
share with you:http://msdn.microsoft.com/en-us/library/ms143755.aspx

C) How to: Run a Package Using the DTExec Utility, there is an article to
share with you:http://msdn.microsoft.com/en-us/libr...3(SQL.90).aspx

There is an article http://msdn.microsoft.com/en-us/library/ms162810.aspx

"Jeff_B" <JeffB (AT) discussions (DOT) microsoft.com> wrote

Sorry I was not feeling well Wednesday and was out sick on Thursday. I
missed that you were using SQL Server2005. I don't actually know anything
about this issue. I just knew that the issue was discussed in the 2008
Release Notes. It looks like that may not be helpful.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jeff_B" <JeffB (AT) discussions (DOT) microsoft.com> wrote