Can you create a graphical view of a database using SSDT? - sql-server

I have just started using SSDT. Is there any way I can get a graphical view of my database and the relations between the tables?
Thanks!

Currently, no there isn't, nor is there any 3rd party plugin for it either (as far as I have been able to establish).
There was some talk a while ago about it possible coming, though no timescales were mentioned:
http://social.msdn.microsoft.com/Forums/en-US/ssdt/thread/853b8ec1-33a2-49c5-9ac2-b93d89e8b859/
Unfortunately, I understand that Gert is no longer working on SSDT, so it may no longer be in the pipeline

There's no diagramming tool within SSDT. You'll have to resort to another tool I'm afraid however that tool will (naturally) require you to deploy your SSDT project first.
A diagramming tool that builds upon the in-memory model that SSDT builds under the covers would be great. Its not there today though.
JT

Related

Replacement for WorkItemFormControl with TFS 2015

Quite some time ago, I implemented a tool for creating and maintaining Work Breakdown Structures in combination with Microsoft Team Foundation Server (you can find it here: http://wbseditor.codeplex.com). It was originally implemented using the TFS 2005 object model, and also relies on the WorkItemFormControl to display Work Items for creation and editing directly from the application. It's quite useful, and is heavily used inside my company for multi-project management.
A while ago, I ported it to using the TFS 2010 assemblies, but now, a couple of years later, I have the need to also support Visual Studio 2015.
In the course of migrating to the new assemblies, I have managed to get all the nuget packages I need (which is Microsoft.TeamFoundationServer.ExtendedClient), but apparently both the WorkItemFormControl (which was targeted for Windows Forms) and the newer WPF equivalent WorkItemControl (from the Microsoft.TeamFoundation.WorkItemControl.WpfControls namespace) are missing.
I suppose I can use a web browser control to achieve a similar effect like before, but I have not found any sample code or similar for this. Does anybody have a pointer how to get a similar effect like I got with WorkItemFormControl? I admit I haven't spent more than a couple of hours on research, simply because I just wanted to do a "quick update" to support the new server versions, and this sort of caught me cold.
Is there a "quick fix" for me I just have been to blind to see?
If there is no such thing as a quick fix, which is the general direction I should head to get the functionality back?
WorkItemFormControl Class is now obsolete, use the WPF version of this control, Microsoft.TeamFoundation.WorkItemTracking.WpfControls.WorkItemControl instead.
To use Microsoft.TeamFoundation.WorkItemTracking.WpfControls.WorkItemControl namespace, you need to add assembly Microsoft.TeamFoundation.WorkItemTracking.Controls which can be added from Microsoft.TeamFoundation.WorkItemTracking.All in nuget package.

NuGet Package Restore Strategies

My sincerest apologies, if this has been asked before. I've searched the site but have not seen an answer for what I'm looking for yet.
For years, my company has referenced custom binaries in a local folder hierarchy within source control. We're in the process of changing our source control, and in the process are defining new strategies for many things. One of the things I've been working on is to setup a local NuGet feed for our custom packages to replace the old source control folder method. I've been able to successfully create custom packages and using the package restore feature, log into our build box to restore both NuGet packages from our local feed, as well as those from the official NuGet feed. Everything has worked well up to this point.
The time has come to begin testing our migration process from our old source control to the new source control, and convert all of the references over to NuGet packages. Where needed, we're creating packages and placing them on our local NuGet server. The issue I came across today involves a project that uses an old version of a vendor library. I searched the official NuGet feed and found the library as a package, but the particular version we used at the time is no longer available.
I know from the fact that package restoration was a highly requested feature, that other companies are already employing the strategy we're attempting now. My question is what strategy is your company implementing when operating under this criteria? Is there a best practice we should be considering?
Thanks for your time and assistance.
That's quite a big question to answer so I'll recommend you some resources to read up on this topic.
I wrote an MSDN article on some patterns and practices I'd recommend when using NuGet into the organization. Maybe you'll find something useful in there: http://msdn.microsoft.com/en-us/magazine/jj851071.aspx.
There's also the book Pro NuGet available at http://bit.ly/ProNuGet.

What is a good, lightweight database to use for a small F# winforms project?

I have a project I'm thinking of doing in F#, but I'm still very new to the language. I'll need a simple database, hopefully something easy to use. Would sqlite work well for an F# project? Other suggestions?
SqlLite is a very popular lightweight database engine that supports a .Net binding layer which is accessible from F#. It probably the best option for your scenario.
This CodeProject article details how to use C# to bind to SqlLite and is easily transferable to an F# scenario
http://www.codeproject.com/KB/cs/SQLiteCSharp.aspx
Another option would be SQL Server 2008 Compact Edition. I don't have any experience with it myself, but my understanding is that it is just a dll that can be easily distributed with your project.
The programming API is standard ADO.NET (which can be easily used from F#). It also supports LINQ, so if you wanted, you could also call it with F# LINQ (FLINQ) from CodePlex.
Check out db4o, it's just an object store, so it's pretty simple.
Firebird embedded can be a good choice too
The embedded version is an amazing
variation of the server. It is a fully
featured Firebird server packed in
just a few files. It is very easy to
deploy, since there is no need to
install the server. It is ideal for
CDROM catalogs, demos or standalone
desktop applications.

Deploying ODP.NET WPF application

Background: I developed a small .NET 3.5 WPF application that connects to an Oracle 9i database. Thinking that the ODP.NET version had to match the database, I downloaded and used an [older version][1] (9i, release 2, to be more specific) of the Oracle Data Access tools.
I'm basically done the application now and need to deploy it. Then I looked at the deployment story for ODP.NET, thinking it would be included as a prerequisite by ClickOnce and I wouldn't have to do anything. Lesson. Learned.
Everything I've read about deployment for ODP.NET talks about using XCOPY with a newer version of the Oracle tools than what I have used to this point. Not much is actually said about 9i in the documentation I've read to this point.
So what should I do?
Thanks for the help!
Here is a similar post where the answer was to change to use a 3rd party library:
ODP.NET and ClickOnce possible?
I think you area in trouble as changing libraries may involve you doing a full retest of your application - this may of course be easier done than said if it is a small app or you have good automated test coverage. Of course it depends how many computers you are deploying to. Personally I would be more inclined to stick with oracle odp and move to the latest version. If you deploy odp "the hard way" you still get the benefit of click once for future redeployments.

Database for Moonlight

I'm looking for a local database for Moonlight. I checked EffiProz Silverlight database and it seems to work fine with moonlight
Any other databases that work well with Moonlight?
Any database that work with Silverlight should work with Moonlight, if not it's a bug and should be reported to the Moonlight developers and it'll get fixed.
However testing that it actually works with Moonlight before deciding which one to choose is of course a good thing, Moonlight does of course have (as all software) bugs.
C# SQLite is always an option... This fully-managed implementation (port) of SQLite is specifically meant to get around the need to P/Invoke native code and so is a perfect SQLite alternative for apps that require a fully managed database (such as Silverlight apps).
It's hard to answer with so few details but you can check Firebird

Resources