i need to know which tool should i use for my olap. i have a dataware house in sql visual 2012, and now i need to integrate a olap third party tool. Can anyone please help? THe tool represent the data in cubee and visual representation.
Related
I've got an SQLite database defined by an SQL DDL (CREATE TABLE etc.) script and am to derive Entity Framework model classes to work with it.
In the past, when I had an opportunity to try Visual Studio 2013 Ultimate and Microsoft SQL Server in the same situation, Visual Studio allowed me to use "database-first" approach and reverse-engineer the model to create the model classes automatically. But I can't find anything like that available in Visual Studio 2015 Community and SQLite.
Am I missing something or are there, perhaps, 3-rd party tools that can do the job to set me free of mechanically typing all the model code manually?
If you use VS Express you are out of luck, since you cannot install DDEX providers or any other extensions using that edition. Use Community, the download sqlite-netFx46-setup-bundle-x86-2015-1.0.104.0.exe from http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki (see my blogpost here for detailed info: http://erikej.blogspot.dk/2014/11/using-sqlite-with-entity-framework-6.html )
If you use EF Core, upgrade to Community, and install the latest daily of my VS extension SQLite Toolbox, which has a feature to generate an EF Core Model via GUI https://github.com/ErikEJ/SqlCeToolbox/wiki/Release-notes
Is there as way to create database diagram in Visual Studio as a Sql Server Project?
I know it is possible to do it in sql server management studio, but I am also wondering if it is possible to do in Visual studio.
As per MSDN (https://msdn.microsoft.com/en-us/library/y5a4ezk9.aspx) the Visual Database Designer was deprecated in Visual Studio 2013.
If you're using an older version of Visual Studio, note that support for the design tool within Visual Studio stops at SQL Server 2008 R2. (See "Important" box on top of page at https://msdn.microsoft.com/en-us/library/ms171976.aspx )
The short answer: no.
Actually there are two ways that i know In Visual Studio.
Add to project ADO.NET Entity Data model. It creates for you a .edmx file which contains a tables with relation.
More info MSDN. It also install Entity framework.
Open Server explorer > Connection to Database. Select Microsoft SQL Server, Server name=.; (or your PC name) and then choose your database schema.
You can check this video.
I hope it helps you.
I have been looking for solutions to providing source control for my SQL Server 2012 instance. I have looked at Red-Gate's solution but it is outside my price range. Since I already make use of Visual Studio Online (VSO) source control for my .NET projects I was wondering if it was able to provide source control for SQL Server?
I have seen articles (listed below) that discuss using Team Foundation Server (TFS) for source control however I do not have a dedicated TFS server, just VSO.
Use Team Foundation Server (TFS) as your Source Control in SSMS
Using the TFS as a source control repository for SSMS projects
Has anyone made use of VSO to handle source control for their SQL Server database?
I would definitely recommend using Visual Studio Online or Team Foundation Server to hold your database scheme in version control. There is a fairly recent article in Visual Studio Magazine that discusses using the SQL Server Data Tools (SSDT) to be able to make that easier for you: Simplifying Development with Visual Studio Database Projects. SSDT is available for any version of Visual Studio including the Community and Express editions.
Redgate was out of my price range too unfortunately...
The SSDT tools for VS are amazing, and i recently started using it for comparing DB versions - and then generating change scripts.
Here's a start point if you want to get into that...
Other Free Alternatives?
Liquibase
gitSQL
Liquibase - i couldn't get my head around but if you can get it working, it may be better for other databases, if you have the requirement to use other databases.
I use gitSQL - it's free up to 20 tables...
If you have more than 20 tables then it costs $40 - which is still so much cheaper than the redgate solution.
gitSQL are also setting up command line options in a future release, so potentially you could run it via a batch file, and set up continuous integration.
gitSQL are also talking about postgres, mysql editions in the future.
Does anybody know how to get export to XLSX support for SQL Server 2008 R2 Reporting Services without upgrading to SQL Server 2012 or using any 3rd party tools?
Apart from developing your own render? Nope. I haven't been able to find ANY information on that by the way.
Apart from going to SQL Server 2012 (a 3rd party renderer may be more cost effective) you could develop your own ASP.Net app while using EPPlus that would link from the report. This stackoverflow post may help start you off with the code.
I have been looking for a way to migrate and upgrade our TFS 2008 server to 2010 server preferably without losing any data.
I have been looking at the TFS Integration Platform
http://tfsintegration.codeplex.com/
and also Visual Studio 2010 TFS Upgrade Guide
vs2010upgradeguide.codeplex.com
Looking at the document TFS Integration Platform - Migration Guidance.xps using the first link, it seems to suggest that I could preserve all the data by first migrating the TFS 2008 from one server to the other and then upgrade the TFS 2008 to 2010.
Is this true?
Thank you,
Chen
Chen - We just went through this process a few weeks ago. While it's not a trivial matter it can be done. There is actually specific guidance for an upgrade with migration to new hardware in the TFS Install Guide. Take a look at the Scenario: Upgrading Team Foundation Server section and the sub-section named Checklist: In-Place or Migration Upgrade on One or More Servers.
The most challenging part of the exercise for us was the SharePoint setup/configuration, but if you follow the guide closely it should go fairly smoothly. This post may help with the SharePoint piece.
If the database is on its own box then you first need to upgrade to SQL 2008. Once that is done you can install TFS 2010 on a new server, select upgrade during the install and point it to the database server.
If the database is on the same box as TFS 2008 then you first need to backup all the databases and restore them on to the new box with SQL 2008. Then install TFS 2010, choose upgrade during the install and point it to the database server.
It should be. Migration of 2008 from one server to another is primarily a database exercise, but it can get tricky when you are initializing the Application Tier.
To be honest, I thought the TFS Integration Platform migration was providing guidance around moving from TFS 2005 to TFS 2008. My understanding was that TFS 2010 has an upgrade feature included in the wizard that should take care of most things for you. Thus far, I've only installed TFS 2008 from scratch and TFS 2010 from scratch-- I haven't yet tried that part of the wizard.
Another consideration is the database platform for your TFS 2008 instance. In our case, our 2008 is installed on MS SQL Server 2005, and TFS 2010 requires SQL Server 2008, so that's going to make our upgrade potentially a bit trickier.