We are having issues with the TFS cube. I don't think it has been built since TFS was installed. The warehouse seems to be working and has new data it just seems to be the cube that doesn't work.
We tried rebuilding it using the TFS Administrator Console but that made things worse, the data that was in there was erased and replaced by what looks like a blank Database.
I tried deleting the Database so that I could see if the cube was actually being built but now when I run the rebuild it says it's looking for an existing Database so it won't even try.
Now that I have deleted it, how can I rebuild the cube from scratch?
Even if I can retrieve the Database it was empty and I wanted to try building it from scratch anyway to see if that fixes the issue.
The Tfs_Warehouse extracts data from Tfs_CollectionA, Tfs_CollectionB, etc databases, and Tfs_Analysis get data from Tfs_Warehouse database. So no worries when the Tfs_Warehouse and Tfs_Analysis is deleted, it is allowed to create a new one.
Here are the steps how to get it work:
Delete Tfs_Warehouse and Tfs_Analysis from SQL instance in SQL Server Management Studio.
Open TFS Administrator Console, go to Reporting node, and click Edit.
On the Reporting dialog, select Use Report checkbox. And fill the Tfs_Warehouse, Tfs_Analysis and Reporting information separately on Warehouse, Analysis Services and Reports tabs.
Please check this blog for the detailed steps: http://social.technet.microsoft.com/wiki/contents/articles/20113.rebuild-tfs-warehouse-and-analysis-databases-from-scratch.aspx
In addition, by default, Tfs_Warehouse and Tfs_Analysis refreshes every 2 hours.
You can manually refresh the cube to get the latest data: https://msdn.microsoft.com/en-us/library/ff400237.aspx
Related
I've been running into an issue recently when I attempt any tutorials that involve using a SQL database, entity framework, dapper, etc.
When it comes time to publish a database, or utilize an ORM, I'm given duplicate options for the same localdb under SQL Servers. Furthermore, then I attempt to publish, the database doesn't show up under the localdb that I've chosen.
I'm wondering how I go about removing the other SQL Servers and just having the one available.
If you look at the image below, the Browse option gives me two of the same LocalDbs. Plus I also get a 3rd one under \ProjectModels. I'm wondering what's causing this and how it can be fixed since no matter which one I choose, the sql database I attempt to publish doesn't show up within any of them.
My advice is not to use this method to publish the database. (right click to delete)
Please refer to this official documentation.
File-based databases like SQLite or SQL Server Express are designed to store their data in easily transferable files that can be served with your application/site.
"Copy to Output Directory" Property of the database file to "Copy if newer". Just point the address to it.
If you are using a server-based database like SQL Server, MySQL, etc., you need to make sure that the target machine/environment has the same database server installed, and you need to write a deployment script to append the pre-populated data files to the server. This might be troublesome for you.
You can also refer to these links. 1,2,3
First of all, I am new to SQL Server, I always use PostgreSQL as a database, but now I am doing some maintenance of an application that persists on SQL Server, so here I am. I am trying to debug a very large stored procedured. First I tried on SSMS v18, but according to this I have to use Visual Studio, in which I am also new. I follow the instructions and try to connect to the database, but after I hit a new query I get this modal window:
I find it weird that I can see the database tables, views and stored procedures, but am unabled to create queries. So I am thinking it is a silly configuration thing I am missing.
I would appreciate the help, I have spent the whole day reading tutorials, but nothing works.
When database changes are made (tables and column names renamed or eliminated), my shop struggles with broke reports which we react to after deployment. There is no established practice to fix the reports to reflect the changes before going live with the database changes.
I have the databases set up as SQL Server database projects in VS and have them committed to GIT. The reporting services files (.rdl files) are in GIT as well. Googled everywhere to see if a database project can be connected to no avail.
Whenever a database object is changed (renamed a column for example) in a database project, I am looking for an efficient way to fix the references to the renamed column in the SQL Server Reporting Services project.
From my experience, the best practice is using stored procedures as data source instead of writing sql query in the report. that way you can simply edit the query inside report stored procedure whenever necessary.
If not you have to open the report and then edit the query and redeploy the report.
Tip: whenever you come across a SQL query as dataset source in SSRS, change it to stored
procedure ASAP. it's easy, because you already have the query.
I have a SQLServer project in Visual Studio, linked to a localDB instance - I can see the real state of the DB and the project script files and I have a publish script which lets me publish the project to the DB.
But doing this for every change is quite slow, yet this is the only way I know to sync my project and the the actual DB model. Is there a better way to keep the two in sync, even automatically? Many times I test changes only to realise my DB isn't up to date and lose time re-publishing and re-testing.
Irritatingly, when I look at the DB in SQL Server Explorer and do "show code" it shows me the updated version even when it is not applied.
To publish the database schema, right click on the database project > Publish. Verify the target database connection and click Publish. There is no need to generate the publish script at this point. Hope that helps.
I am trying to figure out what the normal workflow should be between a SQL Server Database Project and the actual database in SQL Server (SSMS) once they are in sync. The main reason I am using one of these projects is to keep everything in Source Control.
Here are the steps I took to set things up:
Create the actual database and entire schema in SQL Server Management Studio.
Create a new SQL Server Database Project in VS2015.
Right click the project and import the actual database.
Now that the project is in sync with the actual database, how should I go about making changes going forward? Do I make them in the database project and then republish it or do I make them in the schema? Basically what I am saying is that I am trying to avoid making schema changes during development in both places.
Generally the best practice will be to make changes to the project, check that into source control, and publish the changes to your database as needed. Your project then becomes your source. You can branch it, merge it, and do whatever else is needed to do your development. You won't be republishing your database, though. You'll update your existing one when you publish your project. It will do a diff between your project and the db, then make the appropriate updates/alters to bring your database in line w/ the project.
I blogged about my experiences with SSDT here: http://schottsql.blogspot.com/search/label/SSDT, but there are some other great resources available if you look. There are definitely different ways to do things and what I chose may not fit your environment exactly.