I've installed VS 2015 sp3 + ADLA Tools 2.2.5000.0
When i click Cloud Explorer -> Select a U-SQL Table -> Preview By Running a Job, it runs a U-SQL job that pulls some data to a csv file and next i can preview the file.
But some people show the screen bellow at forums. Where i can find it in GUI? Maybe ADLA Tools installed incorrectly :). Or maybe these people have an access to a beta versions of ADLA Tools?
The screenshot is for a Local table. You should be able to do the same for your Local tables. Right-click a Local table and there will be a "Preview" option.
Related
I want to Generate Script in Azure Data Studio by using Database Administration Tool Extensions for Windows as it is mentioned in these a,b questions.
However, after installing the Database Administration Tool Extensions for Windows, when I right-click on the database, the following items is appeared without generate Script.
Would you please guide me? thanks
Please suggest How to Generate the scripts from Microsoft Parallel Data Warehouse...
I have already tried using SSMS 2016 by using my PDW credentials...
But i failed to Generate the scripts...
Regards,
Abhishek
The first thing I would try is to go to SSMS 2016 and go to the Tools menu and choose Check for Updates. Install the latest update out in the last month or so supports Azure SQL DW which is a similar MPP surface area. It may support PDW but I'm not sure.
If that doesn't work, go the tried and true route. Search the Microsoft download center for Analytics Platform System Appliance Update and then choose the version that matches your PDW. Download the .chm help file. Then you have to right click on the .chm file and choose Properties then unblock it in order to open it.
Then search for "Install SQL Server database tooling for Visual Studio" and it documents how to install SQL Server Data Tools for Visual Studio and connect SQL Server Object Explorer. Then you can expand and view a list of tables/sprocs/etc and script them out by right clicking on a table or sproc in SQL Server Object Explorer.
I'm trying to publish a DB project in Visual Studio 2013 Professional and the "Publish" button do nothing.
In project properties I checked "Create script (.sql file)". I right click the project name in solution explorer > Publish... > Load Profile (a profile that works for my colleagues) > Publish
Nothing Happens, not an error, warning or anything (same with "Generate Scripts" button).
Visual studio error logs say nothing and I tried to restart the PC, Visual studio and SQL server.
Thank you!
If you have an Azure Cloud Explorer window open in Visual Studio (could be table, blob or queue), that leads to the Publish of an SSDT project hanging.
Close the window and start a new Publish operation. It may take a little longer than usual but eventually that will progress and you'll be able to close Visual Studio as normal.
Thanks to Noel Abrahams for his comment that led to this answer.
EDIT: putting it here as an answer so that it can be more easily found but credit goes to Noel.
Found a fix on the MS Connect site.
In my publish profile I had set the connection string as so:
<TargetConnectionString>Data Source=.\sql2008r2;Integrated Security=SSPI;</TargetConnectionString>
According to the comments on Connect, it doesn't like Integrated Security=SSPI. Instead you should use Integrated Security=True;:
<TargetConnectionString>Data Source=.\sql2008r2;Integrated Security=True;</TargetConnectionString>
Then it all works fine.
I cloned the solution from VCS to a new directory and only this helped.
Other symptoms that I had with this issue:
While editing a table .sql script, Design pane didn't work.
Integrated Security=True; was set in my publishing profile. So Rhumborl's answer is not about my case.
If the solution folder is copied to another machine the issue is reproduced there too.
I tried to Clean Solution before re-cloning, but it didn't work.
For me publishing the database project to a new sql server database with a different name allowed the publish to proceed. Once I'd done that I was then able to publish to the original database again.
I found that having an Azure Queue or Blob Storage opened in Visual Studio Professional 2015 meant that clicking Publish did nothing and I couldn't close the application. After closing those windows which I had launched from the Cloud Explorer, I had to click Publish once again to kick it off. A strange bug.
I have a SQL Server Scripts 2012 Project with multiple SQL queries and stored procedures.
We use Team Foundation Server 2012 to manage our source code for our Visual Studio Solutions.
How can I check in a SQL Server Scripts 2012 Project into TFS? If it is not possible how can I manage source control on this and allow multiple developers access to it?
You have a few options, here are two that I have used.
1: Download the TFS 2012 MSSCCI Provider:
This plugin allows you to access TFS from Microsoft SQL Server Management Studio. So you can easily add and check in\out those ssmssln and ssmsproj files from TFS.
64bit Download - 32bit Download
Once installed, in SSMS go to Tools-> Options -> Source Control to select the plugin.
If you don't see it then you probably need to install the other bit version.
After you have selected the plugin in the options window of SSMS, you will have a new menu option under "File" that will allow you to Add\Open\Change items in TFS from Sql Management Studio.
To add your Scripts solution using the MSSCCI plugin:
Open the project in SSMS, go to File -> Source Control -> Add Solution to Source Control
2. Add through VS using the "Add files to Source Control"
See here: To add a file that is not in a solution to version control
I'm not quite sure why it would be a challenge to add the sql server scripts to TFS just as any other file in your visual studio solution. I've done this in a lot of projects with great success.
What is a challenge with databases though is to find a good strategy to handle branches and database versioning. I recommend that you have a look at Entity Framework Code First Migrations which handles this very nicely. Another approach is to use Chuck Norris Round house which is a more script based solution:
RoundHouse
https://code.google.com/p/roundhouse/
Code First Migrations.
http://msdn.microsoft.com/en-us/data/jj591621.aspx
If you start from scratch I would recommend the Code First Migrations approach, but if you allready have a lot of .sql files the second can work very well.
The latest versions of MSSCCI still don't seem to work with SSMS 2012 - you'll need an older 32 bit version, here: http://visualstudiogallery.msdn.microsoft.com/en-us/bce06506-be38-47a1-9f29-d3937d3d88d6
Once this is installed you'll be able to see the "Team Foundation Server MSSCCI Provider" in the SSMS Source Control Plug-In selection.
I've switched to Eclipse Juno, which claims not to support SQL Explorer. So I want to start using the stand-alone SQL Explorer, but I don't want to have to re-enter all my connections.
Where does the Eclipse SQL Explorer plugin save its settings, and where does the SQL Explorer stand-alone app store its settings, so I can copy them over?
So, after some research, I have an answer. The Exclipse SQL Explorer settings are stored in
<your-workspace>/.metadata/.plugins/net.sourceforge.sqlexplorer/
The same is true for SQL Explorer. However, SQL Explorer doesn't give you any way to specify the "workspace" to use. On the Mac, you need to "Show Package Contents" on the SQL Explorer app, then drill down to Contents/MacOS/ to find the workspace folder.