I am using Visual Studio 2019 I installed the SSDT tool I created a DB project. But my requirement is that I need to create different sql database for each client. Is it possible by Using SSDT package. I only create table, stored procedure, functions, views etc. but not Database.
Please provide me a way to develop it. Is there any Azure API by which we can create database for each client?.
Related
When I am trying to Install TFS it is asking me to "Install new SQL server" or "Use the existing SQL server". If I have existing SQL server which is used by the Application ( all the application related tables ,SP..etc) and if I choose to select the "use the existing data base" while installing TFS. Will that effect in the performance of the application? Because application uses the same database as well Tiffs also uses the same database.
Wondering if some one can suggest me what is the best practice to use the same data base which is used by application or use the different database for TFS.
Yes, if you have two applications using the same database server you will likely have a performance impact, dependent on capacity/performance of the servers.
I would recommend that you instead create an account on http://tfs.visualstudio.com and use the hosted TFS. It's more secure, has backups, and is supported and managed by Microsoft for you. You get 5 users included over and above any MSDN users that you already have.
If you are intent on running your own server then TFS included a SQL Server standard license if you are running on a single server, and only use it for TFS. So I would install SQL Standard and then TFS 2017 and select Existing. If you get TFS to install its own SQL it will use Express...
I am planning my migration from TFS 2010 to TFS 2013. I am using the guide at http://vsarupgradeguide.codeplex.com/downloads/get/755804#
Currently my TFS 2010 server has a reporting services instance installed with the required databases:
Tfs_Warehouse
Tfs_Analysis
ReportServer
ReportServerTempDb
Can I migrate to a new TFS 2013 server without backing up / restoring the reporting services? Basically not installing reporting services and then just later on installing a new instance of reporting services?
Will this work or will the migration process fail? Will I lose any functionality if I do it this way?
If you switch over to a new instance of reporting services without backing up the database and the encryption key from the old one, you'll lose any custom/modified reports, as well as have to re-apply security settings. Other than that, there's no harm in it.
The warehouse and analysis databases are not part of reporting services, they're the TFS warehouse and analysis cube databases. They're created by TFS.
The ReportServer database is the one that holds all your reports.
I need to extract some data from TFS (Team Foundation Server) and create some excel sheet with data. To automate it, I am writing an application . But problem is:
How can I get data from TFS? Is there any webservice available for this or I need to parse HTML and then get the data.
No. TFS has broad coverage APIs and came in two flavors: Object Model and REST.
The Object Model is automatically installed when you install Visual Studio / Team Explorer, otherwise you can use the stand-alone MSI. This is a .NET API, but you can also find the Java version in case you need it.
The OM is simple to use for a .Net developer.
The REST API are kind of new and you should study if they satisfy your requirement. Some APIs are supported only on VSO and they miss from TFS on-premise and older versions.
We want to maintain our sql server scripts history. What is the solution? can we integrate SQL Server Management Studio 2008 with TFS 2010?
Sure, there is, a DB professional which is a project type in the visual studio, this type of project will maintain DB objects as separate files so it can be treated as normal C# or VB file, for version control.
SSMS is able to save sql files to SCCI compliant source control systems, such as TFS. Here is an article explaining how to achieve this.
However, this just saves sql files but doesn't assist in the versioning of the schema objects in your database. Should you need to do this, SQL Source Control, which we have developed at Red Gate, allows you to connect your SQL Server instance in SSMS to your back-end source control system, such as TFS.
How exactly does that integrate with SSMS??? You can still go behind the scenes with ssms and edit whatever you want, regardless of source control.
I am using SQL Server as a database and TFS 2008 as Source and Version Control. When I create a object in database respectively I will create the object in TFS as a sql file.
I am facing problem like some developers creating object in Database but they are not updating the TFS with the same.
How do I maintain the TFS and Database in sync and if any differences are there, how can I find easily ?
I would propose to only allow developers to add and modify SQL scripts in your TFS system. Then use build automation to execute those scripts against a clean database. That way, you are always 100% sure you can reproduce your database model and content from the items you have stored in TFS.