I have installed ssis file watcher task on my laptop which is running a local copy of sql server 2012 and visual studio 2010.
My question is once i have built the ssis package and wanted to run it on a different server do i also need to install the ssis file watcher addon on the server as well as my laptop??
The short answer is yes.
SSIS does not come with an in-built file watcher task, so it sounds like you installed something like this: http://www.sqlis.com/post/file-watcher-task.aspx. In order for the server to be able to execute the package it will be looking for the file watcher ell in the GAC. The task I noted here has an msi file which will take care of the installation process. If the task does not, the least that you need to do is just get the dll in the gac, it does not need to go in the sql server folders which are only necessary for development.
Related
I've carried out a lot of work here and want to be able to use my DTSX packages
But I get the version incompatibility and the Error message is specific
But there must be some way I can run my packages. They appear to not be able to be run from within VS2013 Pro editor
My question is, what do I need to install exactly to all allow me to execute these saved packages?
By asking here i can save time since there are many versions and many add ons etc
First - how to run a SSIS 2008 package?
There is a good overview here, by Ashish Kumar Mehta of MSSQTips, on how to execute packages both remotely on the server or locally. Either way you need the SQL Server Client Tools installed from the SQL Server media (CD, image, etc.). There's no possibility of running a package locally from Management Studio or raw Visual Studio. You can run the package remotely through Management Studio only if that package was stored within the SQL Server. Theoretically, you can run a package in development mode via VS2013, see below.
Second - how to modify a SSIS 2008 package?
Unlike subsequent SQL Server (and SSIS) versions, with 2008 you couldn't just use your regular Visual Studio with a downloadable plugin. You had to install one Business Intelligence Development Studio (BIDS), a Visual Studio 2008 derivative (i.e. not a plugin) available on your SQL Server media. That's the way to go if you want to edit the package but also maintain its 2008 version. Otherwise, you're free to upgrade the package to Integration Services 2014 level by several methods, and start hacking at it via Visual Studio 2013 with a downloadable Data Tools - Business Intelligence plug-in. Be advised, it's not possible to convert the package back to 2012 nor 2008 versions.
I have a bunch of programs set up as prerequisites in the VS bootstrapper. Recently, everytime I build on my machine and try to run setup.exe, I get an error ".....msi has either changed or been corrupted since the package was originally published". I know this isn't a problem with the setup or the msi files because I done the exact same thing on another development machine and copied the output to my machine and it's worked. I figure it must be something within the visual studio - bootstrapper connection. Anybody have any ideas?
Have you tried checking the log file ActivityLog.xml. It's under AppData\Roaming\Microsoft\VisualStudio\10.0
You need to run Visual Studio this way "Devenv /log"
I know there are ways of installing SQL Express from the command line. This link gives an example of that. There is another example in here..
When I make this change in my application:
then when I deploy my application and install it on a computer that does not have that prerequisite I notice that the installer downloads that prerequisite:
If I cancel the installation and then launch the exe file that the installer downloaded then I will see:
If I do not cancel the installer, I believe that the installer then goes ahead and installs SQL Server Express with a technique similar to the one posted by the first two links link 1, link 2.
Where does Visual Studio stores the parameters that are being passed to the exe that it downloads in order to create a silent install? will it be possible to modify those parameters that are being passed to the exe? also I know which file (prerequisites) did visual studio (installer) downloads because I found it on the computer when installing my application but how can I tell from what link does visual studio downloads the prerequisites? I know it depends on the OS version and architecture of the operating system where the application is being installed.
Anyways I am just curious about the last paragraph. In short, I just want to modify the parameters that are being passed to the prerequisites of SQL Server Express 2008. Those parameters should be somewhere in the application that I deployed. Or maybe they get downloaded from Microsoft.
On a 64-bit machine the SQL Server Express bootstrapper is typically located in the following folder:
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\SqlExpress2008\en
Look inside the package.xml file for the command line parameters for the installer.
Looking into installing an instance of SQL Express for an app. I want to have a separate installer. (I need to run some Transact-SQL stuff afterwards)
I've been referencing this article.
It is recommended that you ship the Express package extracted on your media and then launch Setup.exe directly. To extract the Express package, run the following command.
So far I tried bundling the unpackaged SQL Setup in an MSI (using a Setup and Deployment project). The user installs, which just puts the extracted files in a folder, then in OnAfterInstall I'm the setup process. This doesn't work since SQL's Setup.exe runs some .msi files.
Was able to make my own executable to bootstrap the installation and use FreeExtractor to create a self-extracting zip of the setup and my bootstrapper and then run my executable at the end.
I have a DBPro (DataDude) project inside my solution to manage and version the database schema of my application. I use TeamCity 4.0 for continuous integration.
To be able to build a .dbproj, MSBuild tasks and their respective assemblies have to be installed, other .dbschema and .xsd dependencies put in place. The easiest solution is to install VS2008 TS: Database Edition on the build server.. something i'd love to avoid. I have started putting the files in place one by one bot got bored after the build failed on some missing XSD files installed by VSTSDB.
Has anyone found an easy way to avoid installing VSTSDB? A community-made 'redist' installer that puts the right files in the right place and the right assemblies into the GAC? The topic is pretty hard to google so I am hoping to tap the stack overflow knowledge base :)
I am aware of the Deploy folder and vsdbcmd.exe but I would like to build (and deploy).
No. Not according to this post by Gert Drapers
The question is if you are able to build the db using command line (like devenv.exe with some arguments)? If so I see no problem installing the dev environment and executing through a command line task in MSBuild on the build servers. I do the same thing for MSI installers in the projects I manage.