Problem
I can't figure out how to ignore users in my vs 11 beta sql server db project when publishing.
Why is this a problem
This is a problem because I want to keep the setting where I want to drop objects that are not in my project but are in the db being published to. If I delete a sproc in my project I'd like to drop the sproc in my db.
Any ideas? I've looked at all of the publish settings and just can't seem to figure it out....
Encountered this as well, since it persists in Visual Studio 2012 RTM / SP1 with SSDT (SQL Server Data Tools). I reached out to Barclay Hill at Microsoft who works on the product, who confirmed that this is currently not possible:
It is frequently asked for i.e drop everything, but users, permissions
and roles. We have it on our backlog, but have not been able to get
to it yet.
Related
I have multiple Azure SQL databases. One database holds all the staging table and the other database holds all the fact/dim tables. Now in my development environment I have stored procedure which reads data from staging tables (from staging database) and loads the data into its respective fact/dim tables (in a different database).
The above scenario is all working fine. I have multiple SQL projects for each database.
Now how do I deploy the elastic database queries while deploying the dacpac?
Below is the error when I add the elastic queries as a part of my post deployment scripts in Visual studio and try to build it.
PS: The SQL project properties is set to target the V12 version of the Azure SQL Database
Which version of the SQL Server Data Tools (SSDT) are you using? If you are not using the latest (14.0.60413.0), give it a try to upgrade SSDT: https://msdn.microsoft.com/en-US/mt429383. With that version, I am now successfully able to compile and publish database projects and dacpacs.
To successfully build, you will need to install the latest SSDT Preview which includes support for these objects from here. Support for the latest Azure SQL DB and SQL Server 2016 features is only available in the Preview for VS2013 at present, whereas for VS2015 the support was shipped in VS2015 Update 2. Once SQL Server 2016 goes GA (June 1, 2016) an RTM update will be pushed through the Visual Studio 2013 Extensions and Updates channel containing this support. That will ensure you get monthly updates with the latest changes again.
Note that even with the latest bits, if you open the file itself you'll get an issue with the Intellisense parser. Building the project will work fine but on opening a document you will see the errors appear for that specific document. Note that the same issue occurs in SSMS when coding this into a query window. This is because the Intellisense parser is separate from the core build system. The fix for this is in progress and will land in a post-SQL Server 2016 update (likely late June - July timeframe).
Disclosure: I work on the SQL Server tools team.
I'm trying to add a Project Data Source in a GridView in DevExpress.
I click on the little arrow on the above right of the Gridview. I choose 'Add project Data Source'.
Then I choose, a Data Type source => DATABASE.
Then, 'Database model' =>DATASET.
Then, for 'Data connection' I choose MS SQL Server.
I then choose the server and I get a pop-up windows that says:
This server version is not supported. You must have SQL Server 2005 or later.
Now, I've confirmed that the server I'm trying to connect to has Microsoft SQL Server 2000 installed on it.
I know that some people got that pop-up window when trying to use Microsoft SQL Server 2008. It was apparently a Visual Studio issue.
I just want to confirm that this message that I'm getting is legit. (It would seem right, seeing, as I
mentionned earlier, I have Microsoft SQL Server 2000 installed. ) For some reason, I still
think it's weird that I'm getting this message. I have Microsoft Visual Studio 2012 by the way. Can anybody confirm this.
I do not think that this issue is related to DevExpress control. It is common issue with visual studio when you SQL Server that Visual studio IDE does not support or missing SQL Server Data Objects.
I suggest you to check below link for your confirmation that SQL Server is not supported in newer IDE directly.
This server version is not supported. You must have Microsoft SQL Server 2005 Beta 2 or later.
SQL Server 2000 and Visual Studio 2010
This Server Version is not supported. You must have SQL 2005 or later (VS2010 Problem)
Some how you can use quick fix to connect with the data base and write code to do other operations.
Connecting SQL server 2000 using Visual Studio 2012
.NET Framework Data Provder for OLE DB -> Microsoft OLE DB Provider
Hope this help you understand the real issue behind this.
We’re running TFS 2013 Update 1 and I’m planning an upgrade to TFS 2015 Update 1.
We have both SharePoint and Reporting Services installed and configured for TFS that I like to remove, because nobody ever uses them.
So, do I simply uncheck both Reporting and SharePoint during the TFS 2015 upgrade wizard. Is this the best way to do it?
Or, do I un-configure Sharepoint and Reporting Services first from our TFS 2013 installation? If so, what are the steps to do so?
Environment:
Server computer A:
Application tier for TFS 2013 Update 1
Data tier: SQL Server 2012 SP 1 for the TFS databases, and Reporting Services databases
Sharepoint services (only for TFS)
Server computer B:
SQL Server 2008 R2 hosting the SharePoint databases.
You can do either.
I'd probably uninstall/disable first if you're really sure you don't want them in the future (check with all the teams that they're not storing docs in SharePoint as they will lose them). That way the backup will be smaller/faster when you backup before you upgrade (Make sure you take a backup!!).
It's simple enough to do, just fire up the TFS Administration Console.
Select Reporting, Edit (this will stop the jobs) and uncheck "Use Reporting". Click OK.
For SharePoint, click SharePoint Web Applications and under the top section, click Modify against your server connection and choose Remove.
Make sure you take a new backup at this stage and then you can start the upgrade.
Some things to consider:
Are you sure you want to do this in-place? You could clone the server to new hardware and test the upgrade first or perform a migration upgrade. It means less downtime in the event of something going pear shaped.
If your collection(s) are large, this is likely going to take a long time. The 2015 upgrade seems to be slower than previous upgrades due to all the schema changes.
Are you sticking with a single server? That's fine, but you won't need server B for SharePoint so you could move to a dual server TFS install if capacity is a problem (You'd need to upgrade the SQL version on server B to act as a data tier though)
I'm a couple years late, but this still popped up in a search result so worth mentioning - use cmd prompt to do this:
Navigate to %programfiles%\Microsoft Team Foundation Server %#%\Tools\, and type TfsConfig.exe setup /uninstall:SharePointExtensions . This will "unconfigure" the feature in your App Tier.
I ve done some research and i can't seem to find anything similar to this.
I have an SQL Database from Windows Azure with several tables. I can log in just fine and view all the table data of all tables, except from a specific table.
When I click on the "Data" section of that specific table, my screen just goes completely blank and then I can't do nothing about it, apart from starting over. Any thoughts on this ?
(I have the latest version of Silverlight installed and I ve tried with Chrome,Firefox and Opera)
Thanks
You can use SQL Server Management Studio (SSMS) 2008 R2 for browse or what ever the task you have to do with SQL azure database as a alternative for your way of method.
Using SQL Server Management Studio 2008 R2 to Manage SQL Azure sample screen is as below.
For more information check this out Getting Started with SQL Azure Development
UPDATE
If you're going to use express edition, then you have to use SQL 2012 express with Win 8.
Check this out SQL Express Edition 2012
I hope this will help to you.
I'm creating a CRM 2011 plug-in. I created it with the Visual Studio Solution Template for Dynamics 2011, and authored it as a CRM 2011 Plug-In Library. After completing the iniital implementation and testing in CRM, I now need to associate the plugin with a different Entity / Attribute / SDK Message. So...I re-opened VS to try to create another plug-in or to otherwise edit it this one.
Oddly, I get a WCF Error from Visual Studio's IDE when I re-start an existing SLN that used to work. Specifically, I get the error when I start the CRM Explorer in VS. The error is pretty generic -
The server was unable to process the request due to an internal error. etc .etc.
The CRM Explorer tree shows 0 Entities and 0 Option Sets after the error, though the other tree nodes seem to have the correct content. It feels to me that something in my Org or CRM Server has broken the VS integration, but don't have any idea what that might have been. I mean I hadn't made any changes to the Org at all in a week or so (though I did apply August Windows Updates!). I'm on Cum Update 8 at the moment.
When I delete the hidden blah.SUO and the blah.docstates.suo files, and restart VS ... the CRM Explorer prompts for my server / credentials / Org as expected for the initial start. However, I get the above WCF error again and the CRM Explorer does not populate correctly following this "reset". I have also tried uninstalling the CRM Developer Toolkit without luck.
Anyone seen this behavior before, or have any suggestions?
I have seen something like that happen when the WCF endpoints were re-configured (CRM Deployment Manager). You can check to see what the endpoints are in the Settings - Customizations - Developer Resources
I had a similar issue: trying to connect to CRM Server through development toolkit add-in to VS.
Resolution: add the user to the CRM Organisation and assign role "System Administrator".