Can I use Visual Studio Community in my company to develop Integration Services, Analysis Services, and Reporting Services?

Hey guys! How are you?

Today we are going to dive into a topic that generates a lot of confusion in the minds of DBAs, BI developers and IT managers: the evolution of development tools for the SQL Server ecosystem and, mainly, the controversial licensing of the Visual Studio Community for data projects in the SQL Server BI stack.

I am often asked: “Dirceu, I work in a multinational company, can I use Visual Studio Community to develop my SSIS packages or my Analysis Services cubes?” The short answer is: YES, and I'll prove to you why using Microsoft's own documentation, as well as going through the entire timeline since the heyday of BIDS.

The BIDS Era: Where it all began

For those of you who are old school like me, you may remember the BIDS (Business Intelligence Development Studio).

This product appeared in SQL Server 2005 and was consolidated in versions 2008 and 2008 R2. At that time, the experience was tightly coupled with the SQL Server installer. You opened the SQL “Setup.exe”, selected the client tools and, magically, you had a minimalist Visual Studio 2008 installed on your machine, focused exclusively on BI projects.

BIDS was robust for its time, but suffered from the mismatch between Visual Studio versions and SQL Server versions. We were often using VS 2008 to develop for a database that already supported much more modern features.

The Transition to SSDT (SQL Server Data Tools)

With the arrival of SQL Server 2012, Microsoft changed the nomenclature and strategy. BIDS died and gave way to SSDT (SQL Server Data Tools).

Here began a phase of some confusion, as there were different versions of SSDT: one for Database Projects (the former “DataDude”) and another for Business Intelligence (SSAS, SSIS, SSRS).

During this period, Microsoft started to make the “Visual Studio Shell” available. It was a free and limited version of Visual Studio that only served as a “host” for BI project templates. If you didn't have paid Visual Studio (Professional or Enterprise), the SSDT installer installed this shell for you.

The Visual Studio Community Milestone (2015 to 2026)

Starting with the 2015 version of Visual Studio, the game has completely changed. Microsoft released the edition Community, replacing the old “Express” editions.

The idea was to provide a complete tool (with support for extensions, refactoring, testing, etc.) for independent developers, small companies and open source projects.

However, for our SQL Server world, there has been a fundamental technical change. SSDT went from being a “stand-alone” installer with its own Shell to becoming a workload or an extension within Visual Studio.

Performance and Architecture: 32-bit vs 64-bit

A crucial technical point in the evolution was the migration of Visual Studio to 64-bit, which occurred in version 2022. Until VS 2019, the design environment (devenv.exe) was a 32-bit process. This greatly limited the development of complex SSIS packages or gigantic SSAS tabular models, as Visual Studio often crashed due to lack of memory (the famous OutOfMemory error).

With VS 2022 and now 2026, the development environment is native 64-bit. This allows you to manipulate much larger metadata without the IDE crashing.

Evolution of Versions: From 2015 to 2026

Below, I prepared a comparative table on how BI tools behaved across Visual Studio versions:

Community Licensing in “Enterprise” Companies

There is a topic in Community license terms that companies with revenues exceeding 1 million dollars or more than 250 computers (Microsoft's definition of “Enterprise”) are strictly prohibited from using the Community edition.

If you just read the license summary, you might come to this conclusion. But the secret is in the exceptions. Let's analyze the official text of the license (versions 2022 and 2026):

There is an item in Visual Studio Community License 2022 which says the following:

1) INSTALLATION AND USE RIGHTS
the. Individual License: If you are an individual working on your own applications, whether to sell them or for any other purpose, you can use the software to develop and test these applications.
b. Organizational License: If you are an organization, your users can use the software as follows:

1. Any number of your users may use the software to develop and test applications released under free software licenses approved by the Free Software Initiative (OSI).
2. Any number of users can use the software to develop and test extensions for Visual Studio.
3. Any number of users can use the software to develop and test device drivers for the Windows operating system.
4. Any number of users may use the software for Microsoft SQL Server development only when using SQL Server Data Tools or the “Microsoft Analysis Services Projects”, “Microsoft Reporting Services Projects” or “SQL Server Integration Services Projects” extensions to develop Microsoft SQL Server database projects or Analysis Services, Reporting Services, Power BI Report Server or Integration Services projects.
5. Any number of your users can use the software to develop and test their applications as part of online or in-person classroom training or to perform academic research.
6. If none of the above conditions apply and you are also not a business (defined below), up to five of your individual users may use the software simultaneously to develop and test their applications.
7. If you are a company, your employees and contractors may not use the software to develop or test your applications, except for: (i) open source software; (ii) Visual Studio extensions; (iii) device drivers for the Windows operating system; (iv) SQL Server development; and (v) training purposes as previously permitted. “Enterprise” is any organization and its affiliates that collectively have (a) more than 250 PCs or users or (b) more than one million US dollars (or the equivalent in other currencies) in annual revenues, and “affiliates” means those entities that control (through majority ownership), are controlled by or are under common control in an organization.

In Visual Studio Community 2026 license, we have the following text:

2) INSTALLATION AND USE RIGHTS
the. General provisions: Subject to (b) and (c) below, one or more users may install and use copies of the software on their devices to develop and test applications. This includes using copies of the software on your own internal servers that remain fully dedicated to your own use. However, you may not separate the software components (except as otherwise indicated in these license terms) and run them in a production environment, on third-party devices, or for any purpose other than developing and testing your applications. Running software on Microsoft Azure may incur separate usage fees.
b. Individual License: If you are an individual working on your own applications, whether to sell them or for any other purpose, you can use the software to develop and test these applications.
w. Organizational License: If you are an organization, your users can use the software as follows:
– Any number of users can use the software to develop and test:

1. applications released under open source software licenses approved by the Open Source Initiative (OSI)
2. extensions for Visual Studio
3. device drivers for the Windows operating system
4. its applications as part of in-person or online training and education, or to conduct academic research
5. Microsoft SQL Server database projects or Analysis Services, Reporting Services, Power BI Report Server, or Integration Services projects when using SQL Server Data Tools or the “Microsoft Analysis Services Projects,” “Microsoft Reporting Services Projects,” or “SQL Server Integration Services Projects” extensions.

– If none of (1) to (5) above apply, and you are also not a company (defined below), up to 5 of your individual users may use the software simultaneously to develop and test their applications.

d. Business use

• An “enterprise” is any organization and its affiliates that collectively have (a) more than 250 PCs or users or (b) more than one million US dollars (or the equivalent in other currencies) in annual revenues, and “affiliates” means those entities that control (through majority ownership), are controlled by, or are under common control in an organization.
• If you are a business, your employees and contractors cannot use the software to develop or test their applications, except for the uses listed in Section 2(c) above.

This is extremely valuable information for the DBA who needs to justify the installation of the tool to the Compliance or Audit team. You don't need to spend thousands of dollars on Professional or Enterprise licenses if your team is just going to build data pipelines in Integration Services or Analysis Services cubes.

Conclusion

The evolution of Visual Studio to the SQL Server ecosystem shows Microsoft's maturity in separating the IDE (the development environment) from the server components. Visual Studio Community is a very powerful tool and, as we have seen, perfectly legal for professional use within any company, as long as the focus is on developing SQL Server objects.

Understanding licensing is not only a task for the legal sector, but also for the DBA who acts as a technological mentor in the company, ensuring that the team has the best tools without unnecessary costs.

I hope you enjoyed this post, a big hug and see you next time!