I have the latest version VS2010 express installed and it does not recognise SQL files. The files are opened as plain text. Is there a setting somewhere that will enable VS2010 to view SQL files in some sort of SQL editor?
Thanks
I don't think the express addition supports syntax highlighting for .SQL files.
Related
I am importing my SQL 2008 R2 packages into my SQL 2014 server. I'm noticing there are 2 ways to do this
Integration Services Catelog -->SSISDB
Connect to SSIS -->Stored Packages
I'm trying to understand the difference between the 2 ways. I like the SSISDB way better. Don't ask me why. I just do.
Is one way the "new" way or "proper" way and the other way is just for backwards compatibility?
You can export the SSIS Project to Sql server data tools 2014 by opening the exported ispac file in Visual Stdio 2012 or newer version.
You just right click on the deployed project and export the ispac file to a particular location in your system.
Now, Open Visual Studio and open business integration import project and browse that file.
Here, your packages in that project will be upgraded to newer version of SSIS.
Hope, this could help you!
I have recently migrated my visual studio 2010 projects to 2013 but my database project looks unhappy about it. I have a TFS build definition which helps me deploy the database project and i have specified the (.sln) solution file and the .proj separate file which helps e drop the file to some location. This has been working well when I was using 2010 but right now its giving me the following error.
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I replaced .sln file with the .sqlproj and this seems to fix the failing build definition but I don't get any deployment files.
Do you have any suggestions please, this is blocking my work right now.
You need to set the environment variable VisualStudioVersion=12.0 when building from the command line if you are using VS2013. SQL Projects rely on this to detect whether to use the VS2012 (v11.0) or VS2013 (v12.0) targets file when building.
Normally when a new Visual Studio version is released there's an accompanying .Net version update that changes the default VisualStudioVersion default value, but with VS2013 this didn't happen. Hence SQL Projects (and some other resources with similar version-specific dependencies) require 12.0 to be explicitly set as the version, since 11.0 is the default.
Also when running on a build server you must have a version of Visual Studio 2013 installed that includes the SQL Server tools. Full instructions on setting up a build server are in the whitepaper and presentation on the SQL Server tools team blog.
I am trying to write a .NET program so I can execute a Dts pacakge but I cannot find the Microsoft.SqlServer.ManagedDTS.dll reference so I can then use the namespace Microsoft.SqlServer.Dts.Runtime.
However I have SQL Server 2008 Developer edition installed on my development machine along with Visual Studio 2008 and 2010. Therefore it should be there, What have I missed?
Many thanks
Mike
In References, browse to this directory:
C:\Program Files\Microsoft SQL
Server\90\SDK\Assemblies
hopefully you'll find it there.
The above was for SQL Server 2005. It should be located in your GAC. Have a look in:
C:\Windows\assembly
for the DLL as Visual Studio won't list all of the DLLs so you'll have to browse to it.
For Windows 7 "Microsoft.SqlServer.ManagedDTS" can be found in following path
"C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\"
For SQL 2005
C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies\Microsoft.SQLServer.ManagedDTS.dll
For SQL 2008
C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SQLServer.ManagedDTS.dll
If you still can't find the Assembly, make sure you've installed the Client Tools SDK.
One more option to try if above given solution does not work.
Add a script Task to SSIS ControlFlow Panel. Double click to configure.
Click on Edit Script... Script page will open as project in Visual Studio.
Find the reference Folder under the project.
Here Microsoft.SqlServer.ManagedDTS.dll will be added for you by default.
Click on the Dll and go to property window.
Copy the path.
This worked for me after a trial and error. I am using VS Data Tools trial version.
For dotnet Framework 4.0
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\v4.0_11.0.0.0__89845dcd8080cc91
I'm using LinqToSQL in a 3.5 framework project in VS2K8, running against MS SQL 2k8.
When I create the table mappings using the design surface within Visual Studio everything works fine.
When I create the table mappings using SQLMetal (from the Windows SDK v6.1), SQLMetal complains about about the SQL Server 2k8 datatypes (e.g. date and time) that I'm making use of.
Does SQLMetal support the SQL Server 2k8 datatypes? Do I need an updated version? Or do I have to create my mapping in the visual designer/revert to SQL Server 2k5 datatypes?
Thanks
As far as i know it supports it, so you probably need a newer version of SqlMetal. In the initial version, when Visual Studio 2008 was launched it was not supporting this so probably that's why you have this problem.
According to MSDN:
The SQLMetal file is included in the
Windows SDK that is installed with
Visual Studio. By default, the file is
located at drive:\Program
Files\Microsoft
SDKs\Windows\vn.nn\bin. If you do not
install Visual Studio, you can also
get the SQLMetal file by downloading
the Windows SDK.
I would really appreciate any help for this problem.
Basically I am using SSRS 2008 for reporting services. My choice of DB was MySQL. So I installed ODBC MySQL connector and created a DSN and used it in report design. If I preview the report in the Business Intelligence Dev Studio, I can see the records, but when I try to view in the local URL:
http://mycomputername:port/Reports
it says:
DataSource1 not found or driver not installed.
Can anyone please tell me if this is a problem with SSRS configurations or do I need to make any changes to make it work in a URL-based scheme?
Any custom data source should be present in the rsreportserver.config file located in
C:\Program Files\Microsoft SQL
Server\MSRS10.SQLEXPRESS\Reporting
Services\ReportServer
(Your location will be different depending on SQL Server version /installed path etc.)
More specifically in the < Data > section. I would be surprised if the MySQL ODBC connector would facilitate this.
If it works in the designer, you would probably have a line in the RSReportDesigner.config file located in
C:\Program Files\Microsoft Visual
Studio
9.0\Common7\IDE\PrivateAssemblies
Copy that < Data > line and put it in the rsreportserver.config file.
Rather than ODBC you can install Mysql Connector for .Net ,Download and install the connector after installing the connector open the Report Server Url ,click new data source ,select data source as "MYSQL" on Connection string type the following
SERVER=mysqlserver;DATABASE=database name;USER=username;PASSWORD=password;