Developer hearted / Relational minded - All Comments

re: An “secret” SSIS XML Destination Provider you might not found yet

MRAFFERTY — Fri, 17 May 2013 14:37:46 GMT

Brilliant! be lost without tutorials like this :)

re: Finally, the family…united. SQL Server BI Project templates now available in Visual Studio 2012

JensSuessmeyer — Fri, 19 Apr 2013 05:58:04 GMT

Hi Preet,

that is actually the misunderstanding, the "new instance" does not install a new instance per se. You will be able to install the tools only in the subsequent wizard pages.

-Jens

re: Finally, the family…united. SQL Server BI Project templates now available in Visual Studio 2012

preet sangha _iridium_ — Fri, 19 Apr 2013 01:23:36 GMT

Quick question on a 64 bit environment - what if I don't want a new SQL Server installation. Won't the 'choose new instance' automatically install a SQL Server Express?

re: Script out Jobs in SQL Server

Ikeadale — Thu, 11 Apr 2013 10:11:59 GMT

A good little utility, for anyone interested, two lines of Powershell will achieve the same result:

Import-Module “sqlps” -DisableNameChecking

gci -path SQLSERVER:SQL\<InstanceName>\JobServer\Jobs | %{$_.script()} | out-file -filepath FileSystem::\\SomeUNCPath\All` Jobs.sql

re: Finally, the family…united. SQL Server BI Project templates now available in Visual Studio 2012

Kees Dijk — Thu, 07 Mar 2013 19:46:57 GMT

Hi,

Thanks for this info. But this installation broke my Visual Studio. More details on what happened I posted here : social.msdn.microsoft.com/.../4ae33edc-c1ad-44df-bc74-ffb30ea91287

re: Finally, the family…united. SQL Server BI Project templates now available in Visual Studio 2012

JensSuessmeyer — Thu, 07 Mar 2013 15:57:51 GMT

Thanks, I´ll updated the blog post.

re: Finally, the family…united. SQL Server BI Project templates now available in Visual Studio 2012

Daniel — Thu, 07 Mar 2013 15:47:00 GMT

a comment from Greg Low about architecture mismatch:

Make sure you choose the "New Instance" option (strange as that might seem). Otherwise, you'll get an error that says the following:

Rule "Same architecture installation" failed.

re: Finally, the family…united. SQL Server BI Project templates now available in Visual Studio 2012

JensSuessmeyer — Thu, 07 Mar 2013 15:35:20 GMT

From that point of view, yes. And now comes the big but which cannot be eloborated further here, having the opportunity having things preloaded in the installer as well as having it as a separate download makes sense.

Imagine a future where you don´t have any differences in SQL Server Managment Studio as well as Visual Studio together without any hard borders. :-)

-jens

re: Finally, the family…united. SQL Server BI Project templates now available in Visual Studio 2012

Daniel — Thu, 07 Mar 2013 15:26:27 GMT

"The SP1 installer you are seeing is not purely SP1, this is the instance / feature installer of SQL Server and for my opinion it makes sense going forward to integrate this into the installer making the DEV Tools a "first class citizen" of SQL Server and not of Visual Studio as done in SQL Server Data Tools."

I disagree with the above statement:

the BI stuff is a developer tool and therefore it should be really part of Visual Studio and not SQL Server.

Including SSMS as management studio make sense to be included in SQL Server installer suite but the project templates for SQL Server database and BI stuff is usually not installed on the same machine as a production SQL Server.

Besides that the interval for updates to SQL Server and SSDT are different as updates for SSDT can be released in a shorter intervall as SQL Server

re: Finally, the family…united. SQL Server BI Project templates now available in Visual Studio 2012

JensSuessmeyer — Thu, 07 Mar 2013 13:43:27 GMT

Hi,

I guess right now you are seeing the error message of

"The CPU architecture of installing feature(s) is different than the instance specified. To continue, add features to this instance with the same architecture."

This is investigated and I´ll let you know when there are any news.

The SP1 installer you are seeing is not purely SP1, this is the instance / feature installer of SQL Server and for my opinion it makes sense going forward to integrate this into the installer making the DEV Tools a "first class citizen" of SQL Server and not of Visual Studio as done in SQL Server Data Tools.

Makes sense for me, same for you ?

-Jens