August 6, 2014 at 12:06 pm
Hi all,
Last week I have installed SQLServer 2012 Enterprise. Prior to that, last year I have installed SQL Server 2012, the Express edition.
Enterprise seems to work alright, except for SSIS (as far as I can tell SSAS and SSRS work).
A few days ago I have asked if and how I can SSIS get to work. Unfortunately no useful response to my question.
Today I have searched intenet and on the msdn.microsoft website I found this information:
•You can install SQL Server Integration Services on a computer that has no previous instances of SQL Server.
•You can install SQL Server 2012 Integration Services (SSIS) side-by-side with an existing instance of SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS).
And a little further to the bottom of that page:
* You can only install one instance of the Integration Services service on a computer. You connect to the service by using the computer name.
If this is true (and why shouldn't it be) I see no possibility to get SSIS working.
I came up with the solutuon to delete both instances (why keep express if you have enterprise) and reinstall enterprise from scratch, hoping that SSIS and the rest will work.
Is this the solution?
If yes, I have a next question: how to delete both instances: if I look in "programms and features" of "Revo uninstaller" there are a lot of programs that seem linked to SQL Server. Should I delete them all or is there a better way of doing this?
Thanks in advance
SpeedSkaterFan
BTW: the list in "programms and features" and "Revo uninstaller" are different,
August 6, 2014 at 1:16 pm
Integration services does not come with express so you would only have one SSIS. even so SSIS is a shared feature so even if you installed multiple enterprise instances only one SSIS would be installed, just like SSMS. (http://msdn.microsoft.com/en-us/library/cc645993(v=sql.110).aspx#SSIS)
to uninstall your instances use programs and features. http://msdn.microsoft.com/en-us/library/ms143412(v=sql.110).aspx
From reading you previous post on SSIS not working it seems as though you were having trouble with SSDT and not SSIS specifically. Open SQL Server Configuration manager, Is integration services listed and runninng?
August 6, 2014 at 1:38 pm
Hi Bob,
Thanks for your reply.
You are right about the SSIS / data tools.
If I start data tools (or start visual studio 2010, which is I believe the same), start a new project, choosing integration services / integration services project and then << OK >>, this gives me the message "Microsoft Visual studio is unable to load this document. To design Integration packages in SQL Server Data tools (ssdt), SSDT has to be installed by one of these editions of SQL Server 2012: Standard, enterprise developer or evaluation. To install SSDT run SQL Server setup and select sql server data tools."
When I installed Enterprise the Data tools selection was already chosen, but I could not change it. It was "greyed out" so to speak. I tried to do the installation another time (and hoped that I could change this field it wasn't, again, not possible (so I left this process)
For your question about integration services being listed and running:
SQL server Integration services 11.0 is running and starts automatic.
Can you use this info for my problem?
Hein
PS
The reason why I hoped that uninstalling both instances and installing Enterprise again is that, prior to installing Enterprise on my "regular computer" I did a "test installation" (just to see what happened during installation) on a test computer and there SSDT / SSIS / SSAS and SSRS work fine (that computer has no Express instance installed)
August 6, 2014 at 2:25 pm
SpeedSkaterFan (8/6/2014)
If I start data tools (or start visual studio 2010, which is I believe the same), start a new project, choosing integration services / integration services project and then << OK >>, this gives me the message "Microsoft Visual studio is unable to load this document. To design Integration packages in SQL Server Data tools (ssdt), SSDT has to be installed by one of these editions of SQL Server 2012: Standard, enterprise developer or evaluation. To install SSDT run SQL Server setup and select sql server data tools."
Is there a SQL Server Data Tools if you go to start-all programs-microsoft sql server 2012? do you get the same result if you start SSDT from there?
August 6, 2014 at 2:32 pm
Yes,
I can go to "all programs / Microsoft SQL Server 2012 / SQL Server Data Tools"
I can also go to "all programs / Microsoft SQL Server 2012 / Microsoft Visual Studio 2010"
Both approaches give the same results
Hein
August 6, 2014 at 2:41 pm
I would suggest just uninstall sql server data tools via programs and features. then once uninstalled. try to install it again with the sql server installer selecting only sql server data tools on the feature selection window.
August 6, 2014 at 3:01 pm
In Programs and features there is a program called "Microsoft SQL Server Data tools - Database projects - web installer entry point".
I guess that is the program you are referring to?
If so, if will uninstall that and rerun the installation process.
Hein
August 6, 2014 at 9:07 pm
Once you do have that uninstalled you might be better off getting the SSDT installer here(http://msdn.microsoft.com/en-ca/data/tools.aspx). It is the most up to date one. you would probably want the SSDT-BI version as that is the one that contains project templates for SSIS,SSAS, and SSRS.
August 7, 2014 at 1:38 pm
Bob, let me start by thanking you for all your advise.
This kind of things makes me jumpy, just because it is Terra incognita.
I have spent the best part of the evening reading al kinds of articles, inclusing your suggestions.
Apart from that: before I started installing enterprise I have made a restore point, as well as a image from the C-drive.
I have used the restore point. After this still a lot of SQL server options were available under "all programs".
I then used "programs and features" to uninstall SQL Server 64 bit. This proces gave no problems and there are no (SQL Server) options left in "all programs".
However: there is still an option to start "Microsoft Visual Studio 2010", and that still works. It opens but has only a few options, not the same as there were before.
Also: in "programs and features" there are still a lot of SQL Server programs visible, most are dated on the day Express was installed.
And, not surprisingly, there are references here to Visual studio
If I look in Services, there is no reference to SQL Server at all.
My question: what to do with the remaining SQL Server and Visual studio programs in "programs and features"?
Leave them and install Enterprise again, or should this cause problems?
Hein
August 7, 2014 at 2:18 pm
I dont think it would be a problem but not sure. It might be safe to just uninstall VS as well just to be safe as long as you dont use it for anything else. ie the VS that is install only got installed with SQL server.
August 11, 2014 at 12:50 pm
Hi Bob,
After a (hopefully) well - earned weekend away I have completed the "task" of deleting everything related to the previous installations of SQL Server.
A moment ago I have installed Enterprise again and the installation process was without problems.
The reason for this "excercise" was that SSIS wasn't installed.
Apparently now it is, I have made my first project and that seems to work.
I have to do some more testing but for now I am very happy! 😀
May I thank you for your advise, and guidance. It gave me, as a non - dba, enough confidence to do the job.
Hein
August 18, 2014 at 6:47 am
If you want to treat your windows instance as a scratchpad, installing and uninstalling software multiple times, then do not be surprised if you get unexpected side effects.
If you want to know how SQL Server 2012 will behave on a clean instance of Windows, then always install it on a clean instance of windows. If you want to find if you can get SQL Server to appear to install OK on a server that has had many installs and uninstalls and which may not work in exactly the same was as on a clean install, carry on as you are.
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
August 18, 2014 at 11:47 am
Ed
Thanks for your, somewhat harsch, reply.
The situation that you describe (Scratchpad etc) is just what I wanted to avoid by asking my question.
Just because there are so many SQL Server (related) programs active, I was wondering how to tackle the Uninstall. How to do it right and how to avoid bits and pieces of "old" installs lying around and interfering with a new try.
And because I am extra careful not to damage the system I had, I made, prior to all attempts, a restore point, as well as a systemimage, just to be save.
So I share your concern.
After my thread I have uninstalled and reinstalled SQL Server and so far it all seems to works alright.
Hein
August 18, 2014 at 11:56 am
SpeedSkater is describing what I consider to be a bug in MSSQL. If you have installed SQL Express, you cannot install SSIS on the same machine, even to design packages for other servers. Well you can do the installation, but you will not be able to do any SSIS work.
I found this to be inconvenient to me, as I like to have SQL Express installed on my workstation for testing and experimentation with no approval process hoops or risk of breaking something important. The only solution I found was to uninstall SQLExpress, try installing SSIS, and install SQLExpress again. I didn't want to do this, as I find the more uninstalls\installs you do, the more unstable the system becomes. I ran SSIS remotely on server instead.
August 18, 2014 at 12:11 pm
dan-572483 (8/18/2014)
SpeedSkater is describing what I consider to be a bug in MSSQL. If you have installed SQL Express, you cannot install SSIS on the same machine, even to design packages for other servers. Well you can do the installation, but you will not be able to do any SSIS work.I found this to be inconvenient to me, as I like to have SQL Express installed on my workstation for testing and experimentation with no approval process hoops or risk of breaking something important. The only solution I found was to uninstall SQLExpress, try installing SSIS, and install SQLExpress again. I didn't want to do this, as I find the more uninstalls\installs you do, the more unstable the system becomes. I ran SSIS remotely on server instead.
I have multiple version of express(2008R2,2012,2014) as well as SSIS (2102) and the SSIS data tools project templates(2012) installed on my workstation. I have no trouble designing or executing SSIS packages. I am not sure what kind of trouble you are running against when trying to have SSIS and express on the same workstation.
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply