I took a training on BizTalk 2010 and found very help but I got very confused when i started reading about SQL Server Integration Services, so I have following questions;
Where to use BizTalk vs SSIS?
Does SSIS have VS 2010 project template like we have for BizTalk Server?
For SSIS development which IDE should be used, can we use VS 2010 or need to work in SQL Server Management Studio?
What are the shortcomings of SSIS that BizTalk overcomes?
I think the fundamental difference is that SSIS is designed to run at scheduled intervals or one-off batches. Biztalk is more real-time integration.
I don't know anything about Biztalk, but I do work with SSIS somewhat regularly.
2.Does SSIS have VS 2010 project template like we have for Biztalk Server?
Yep. In the SQL Server installer, install Business Intelligence Development Studio and Integration Services. That will add SSIS templates to Visual Studio.
3.For SSIS development which IDE should be used, can we use VS 2010 or need to work in SQL Server Management Studio?
Visual Studio or BIDS. BIDS is actually just a Visual Studio shell for SSIS, SSRS, and SSAS development. You can do server configuration and interact with the packages you've built from within SSMS, but you do your development in VS or BIDS.
Related
I am trying to do a sql server compact 4 data connection with visual studo 2010 express but I have seen that it is not listed under data connection. Also SQL server compact toolbox here:
http://visualstudiogallery.msdn.microsoft.com/0e313dfd-be80-4afb-b5e9-6e74d369f7a1
when I try to install its says it is not compatible with this version of visual studio (2010 express) so Is there a way to do a data connection to a sql server compact 4? Also servers browsers does not appear in visual studio 2010 express. I want to use and embedded sql server compact in my asp.net mvc4 web application without the need to install any sql server in the machine.
I know that with visual studio 2010 ultimate it is possible, sql server compact 4 data connection can be done and servers browser also appear under view menu. Also I am not sure if with other versions of visual studio 2010,p.e, professional it can be done as well or only with the ultimate.
In conclusion, I want to use sql server compact data connection with my visuals studio 2010 express, is it possible?
Yes, it is possible, but you must you VS 2010 Visual Web Developer Express, and resolve any install isssues according to the blog here: http://blogs.msdn.com/b/sqlservercompact/archive/2011/03/15/sql-server-compact-4-0-tooling-support-in-visual-studio-2010-sp1-and-visual-web-developer-express-2010-sp1.aspx - you can also use the standalone version of the SQL Server Compact Toolbox to open 4.0 files.
We are in a process of migrating our SQL Server 2005 to the 2012 version.
There's a significant number of SSIS (developedn in VS 2005) running on this server.
Will it be ok to just re-deploy these packages on the new SQL instance?
Or will I have to go through the Visual Studio upgrade process for each?
Any comments, advice appreciated.
Thanks in advance.
You're looking at the upgrade, for a variety of reasons.
In 2005, packages would have been stored in msdb.dbo.sysdtspackages90 From 2008 forward, that table was renamed to msdb.dbo.sysssispackages
Even if you deploy them into sysssispackages and kept a 2005 Integration Services Service installed, I don't think the 2005 dtexec would work with the 2008 version of the stored procs in msdb relative to SSIS work. The procs should be backwards compatible for the msdb SSIS "stuff" in 2012 as they poured all of their attention into the 2012 SSISDB catalog and the CLR methods there.
Depending on your Connection Managers, the SQL Server OLE DB connection strings changed from SQLNCLI01 to SQLNCLI1.0 (approximate)
The internals of how Data Flows works has also changed. The mechanism for signaling the end of rows changed between 2005 and 2008 so if you have any custom components, those will have to be reworked.
When you convert from 2005 to 2012, you can migrate to a Project Deployment model or the Package Deployment Model. As it seems you are looking for a minimum of change, stick with Package Deployment Model. The project deployment model will entail forgoing your Configurations in lieu of the fancy new Parameter methodology.
I need to deploy my database to a shared hosting enviroment and cannot use a file-based connection. The Database "Publish To Provider" option is not available anymore in VS2012 Express. I used to work with it in VS2010 and it was very handy. Is there any workaround to this in VS2012 Express? I know can use SQL Management Studio to generate the scripts but i'll have to attach the database for each project as i usually keep my databases in each project's App Data folder. There are also the SSDT but they don't work for VS express editions.
Thanks in advance.
I've ran into problem very similar to this. I have a .dbproj Visual Studio database project. It deploys just fine in SQL Server Express. Now I want to deploy it to SQL Azure - I change the connection parameters but deployment fails with the following text:
C:\Program Files\MSBuild\Microsoft\VisualStudio\v10.0\TeamData\Microsoft.Data.Schema.TSqlTasks.targets(120,5): Error Deploy01234: The target database schema provider could not be determined. Deployment cannot continue.
Done executing task "SqlDeployTask" -- FAILED.
Is deploying .dbproj projects to SQL Azure supported? How do I make Visual Studio deploy the database into SQL Azure? What are other ways to achieve more or less the same results except recreating the database manually using Azure portal?
If you are using Visual Studio 2012, you can now create a Database project and go to Properties - set its Target Platform to SQL Azure in Project Settings tab. Also you can configure the setting for dacpac output. Use this file to import directly as a new SQL Azure database.
As far as I know, Database projects are still not supported by Windows Azure. You can deploy the project to a local SQL server and then use the "Generate Scripts" feature to port the database to SQL Azure. See this link.
An easy solution is to create the database locally and use the SQL Azure Migration Wizard to do the migration up to SQL Azure. It works very well in just a few clicks (and will fix common errors).
Database projects don't work with SQL Azure. What I do is before deploying, create a brand new database on local server (to ensure it is up to date with no dev scripts), and then sync that database to Azure with RedGate SQL Compare. I do a backup first with RedGate SQL Azure Backup.
When we first built DB projects, SQLAzure was still going through its identity crisis and didn't know what it wanted to be. ;)
DBProjects support a significant superset of capabilities vs. SQLAzure. Therefore, it's quite possible that it'll create scripts that won't run against SQLAzure.
I know that the team who took-over the DBProject tooling were looking at restricting the database project generators to output SQLAzure-compatible scripts, but I don't know how far they got or whether they decided to proceed.
I echo dunnry's suggestion above and use the SQL Azure Migration Wizard or Jeremy's and use SQL 2008 R2 and generate Azure-compatible scripts.
I have a reporting services project with lots of reports developed in SQL server business intelligence development studio that comes with sql server 2008. I want to deploy these reports to a server that has reporting services 2005 only but the deployment is failing. I'm wondering if any one around here has been able to deploy reports developed in business intelligence development studio 2008 to a server running reporting services 2005 only.
If it isn't passible, is there a way of downgrading my report project back to reporting services 2005 so i can be able to deploy my reports?.
Unfortunately this is not currently possible.
The following thread contains a discussion from the MSDN forums pertaining to a similar query. If you read through it, you will discover that an MVP raised this as a development/support request with Mcrosoft.
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/686cac48-bc14-4978-b7bf-acbc0c90384e/
Is it really that bad?
For going from 2005 -> 2000, you just had to strip a couple of lines of xml out of the rdl file.
Can't you do something similar? Assuming you don't use 08 specific things like Tablix
?
Microsoft, you don't know how huge of a pain in the butt this problem is. And we're left to find out about this incompatibility only after creating reports in VS 2008 and trying to run them on SQL Server 2005.
This is extremely poor product management on Microsoft's part.