Although SQL Server 2016 is now supported with TFS 2015 Update 3, at present, the TFS Server licence only includes a licence for SQL Server 2014 Standard Edition.
So, Microsoft folk... when will a licence for SQL Server 2016 Standard Edition be subsumed in the TFS 2015 Server licence, and when will the Visual Studio licensing whitepaper be updated to reflect this?
Stack Overflow is a site for programming and developing. (A language-independent collaboratively edited question and answer site for programmers.)
Your question is more related to the products. I have noticed you have asked the same question and got very detailed response from Brian Harry MS in this link. Next time, if you want to get more detailed and up-to-date information about the product TFS and VSO. You can follow Brian's Blog and the news for VSO.
Moreover, for this question according to the response from Brian:
No, it won’t. The solution is to either purchase a newer version TFS
that includes the SQL Server you want or to separately license SQL
Server and manage updates independently (like by purchasing SQL Server
Software Assurance).
Related
I've been doing this for 3 days. I couldn't find the solution. Normally it was supposed to have features like the following.
What is the cause of this problem? And how do I solve it?
You're using SQL Server Express. SQL Server Express is a very cut down version of SQL Server and does not provide anywhere near as many features as Standard and Enterprise; such as database mail (Additional Database Services). If you need features, you need to purchase SQL Server and pay for the edition licences that have the features you need.
If you are using SQL Server for development purposes only, you can use SQL Server Developer Edition, which is allowed to be used for non-production environments only. Developer edition has all of the features that Enterprise does.
You can find the full list of features supplied by each edition here: Editions and supported features of SQL Server 2017
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I have a system that runs on MSAcess and the client want to upgrade this to SQL Server. What version do I need to have on my development machine? If the client has SQL 2010 Enterprise will it be compatible with SQL Express on my development machine? What are the pitfalls of having these two different versions? Will I be able to backup my Express version and restore it to their 2010 Enterprise version?
All help will be greatly appreciated.
Regards
Mac
The best option is a Developer Edition. It has feature parity with Enterpise Edition but, as is only licensed for Developer work and not for production, it costs around $50.
Express Edition is also a feasible choice, as is free, but you'll miss some of the more advanced features and if your client(s) ask for these features you won't be able to test. Examples of useful features you'll miss are SQL Server Agent, Reporting Services, SSIS or Database Mail.
Will I be able to backup my Express version and restore it to their SQL Server 2012 Enterprise Edition?
Yes, as long as you make sure your version is at most the client deployed version and not any newer. You also need to ensure all your application is contained in the database (no dependency on logins, agent jobs etc), which is tricky. But you should absolutely do not do this. Your deliverable cannot be a database binary (mdf/ldf or backup), but it must be a script to deploy the database. If you fail to do this, your will have a big problem after one week when your client will ask for an update. Threat the database as code. See Version Control and your Database. Read about Rails Migrations for a good approach to this problem.
If you develop your application with an Express edition you should not have any problems if the user has a Enterprise edition running.
You can see the feature comparison sheet following this link: Features Supported by the Editions of SQL Server 2008 R2.
P.S. There is no SQL Server 2010. I think you mean SQL Server 2008 R2, thus the link provided links to that content.
If you upgrade your Access Database to a SQL Server Database you might have problems if you use Multiple Values in Access. For further possible incompatibilities follow this link.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am very new to TFS and SharePoint so I hope I can explain myself as best as possible.
We currently run a single server farm that runs on Windows 2007 Standard, SQL 2008, TFS 2010 and SharePoint 3.0. I have been given the fun task of upgrading this to TFS 2012 and SharePoint 2010!
Now I have been following the steps that Microsoft provide but I am still hitting problems along the way and need to know the best possible approach!
I have built a new server with all TFS & SharePoint requirements. Windows 2008 R2, SQL 2008 R2. I have also installed TFS and SharePoint 2010. Before I configure anything I then used TFS backup and restore tools provided with the new installation to back up the existing Database on the old server and restored the databases onto the new server running SQL 2008 R2.
Before backing up the databases I made sure I have a backup of the report server encryption key. When trying to restore this I have the following problem?
Microsoft.ReportingServices.WmiProvider.WMIProviderException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
Have I missed any steps for the upgrade?
Also when performing this upgrade, is there any chance of this interrupting our current TFS & SharePoint production server?
It sounds like you selected "Install but do not configure" when installing Reporting Services. For TFS 2010+ you need to have it configured as the TFS install will not do that for you like it used to in 2005/2008.
I have a blog post that includes how to configure RS: http://nakedalm.com/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/
Although this is for 2013 it applies equally to 2012.
I'm currently in the process of coming up with our upgrade plan for our migration from SQL Server 2005 to SQL Server 2012, and some of our business units still use ProClarity.
I'm aware that this is essentially a "dead" application; where Microsoft isn't upgrading it anymore, and it's scheduled to be EOL'ed in the future.
After googling and digging around on Microsoft's forums, I still can't come up with a definitive answer as to whether the 2012 upgrade will be incompatible with Proclarity. (Business users are on 6.2; which is one minor revision behind)
Has anybody tried this out and been successful? Would we need to keep this portion of the BI tools on SQL Server 2008?
Upgrade was successful, and the users were able to connect to 2012 Analysis Services using ProClarity
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I just bought Visual Studio 2008 Professional and it came with SQL Server 2005 Developer Edition. I'm used to using SQL Server 2005 at work, but the Developer edition doesn't seem to come with Server Management Studio, so I'm at a bit of a loss. A few questions:
What resources are there for configuring and setting up SQL Server 2005 Developer Edition?
What are some resources for managing databases (I know that I can have Multiple Databases with SQL Server 2005), and what 'extras' are provided by Developer Edition?
Are there any funky things I need to know about if I were to create a database and move it from Developer Edition to an actual deployment server?
Are there any other 'gotchas'?
Edit: I've answered the 'Why isn't SQL Server Management Studio showing up' question below. Resources for the other questions are still appreciated.
Any other insights?
OK, If you actually have the full Developer edition on SQL2005 it does have SSMS with it, you just didnt choose that option in the install.
What is more likely is that you installed SQL 2005 Express Edition which does not include SSMS
(SSMS = SQL Server Management Studio)
To manage your SQL instance you should download SQL Server Management Studio Express from here
http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
keep in mind that Express installs with an instance name so your server will actually be MACHINENAME\SqlExpress by default.
And SQLExpress databases are exactly the same as regular SQL Server - the db engine just has limitations when you are running Express.
Good luck.
It does come with SSMS and BIDS but it may not install them by default. Re-run the installer and make sure the 'workstation' (IIRC) bits are installed.
It turns out that installing SQL Server 2005 Developer Edition on a system that also has the Express Edition requires that the user run the setup from the commandline like so:
D:\SQL Server x86\Servers\setup.exe -SKUUPGRADE=1
The other questions are still open to be answered, however.
Developer Edition contains all the features that Enterprise has (or at least most of them). This can be bad if you do not realise.
Some predecessors of mine finished a nice project that required the use of partitioned tables to greatly speed up our creaking DB. It worked a charm. A couple of weeks before deployment it got pointed out that only the Enterprise edition supported partitioned tables. They had to go cap-in-hand to the CFO and the CEO asking for about £16,000 in additional licencing costs.