0 Comments

The documentation for Azure SQL db performance tuning is great and accurate with great detail on docs.microsoft.com (instead of the old msdn location)

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-query-performance

I was looking at a SQL db in Azure and noticed some spikes. Here is my graph:

snip_20170215133957

I could drill into the Azure portal to see what was causing this spike and recognized the SQL statement, so I knew which product to update the SQL for. However this was not even necessary.

Here are the client stats when I copy pasted the query causing the spikes in SQL Management Studio Express. Check out the “Total execution time”

snip_20170215120138

My next step was to take a look at the execution plan of the query. There is this exclamation mark at the sort operation:

snip_20170215120257

When you hover it, you get this context popup:

snip_20170215124310

So it used tempdb. I still had no clue how to fix this, so I reached out to stack exchange. And a user named T.H. gave me the solution to create two rather simple indexes:

CREATE NONCLUSTERED INDEX TEST ON STOCKDEBUGTRIGGERED (ChangeDate)

CREATE NONCLUSTERED INDEX TEST ON STOCKDEBUG(ProductID, StockOld, StockNew)

Here is the query plan after the two new indexes:

snip_20170215124852

No more yellow exclamation mark! and fewer steps. The client statistics also prove that this is a lot faster/better:

snip_20170215124929

From an average of 4250 down to 50!

 

This is also backed by the dramatic drop in resource usage in the Azure Portal:

snip_20170215133957

So the lesson is: do not trust the Azure db perf advisor a 100% Smile

T.H. commented on Stack Exchange:

The automatic index advice is extremely limited, and often misleading, so can only be considered as a starting point.

 

Hope this info might help someone troubleshooting Azure Db perf!

 

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn
0 Comments

I have stored an mp3 in my OneDrive music folder on my Win 10 (build 14393.693) and it syncs to OneDrive online. So far so good. When I go to https://music.microsoft.com

it is not there. When I click on the song on https://onedrive.live.com/ it starts to open music.microsoft.com and I see:

snip_20170208101035

So something is wrong there:

snip_20170208100957

So I cannot play the mp3 which is in my OneDrive music folder. They appear up on onedrive.com so the onedrive sync is working fine. The problem is with my groove connection. When I locally start groove, there is the mp3. Because I stored it on my HDD it loads locally, but does not show up from onedrive.

Local Groove:

snip_20170208101306

I clicked on the option to reset my groove catalog which seems to reset my cloud collection:

snip_20170208101744

This does give me my recently added track. But only as “unknown”

snip_20170208101845

There is a lot which is not known…

Perhaps this all happened because I added the onedrive/music folder which is local as folder to watch for groove:

snip_20170208102004

I have removed that reference now and this seems to fix it Smile Even the new track is not an unknown one!

 

I hope this might help someone

Pin on pinterest Plus on Googleplus Post on LinkedIn
0 Comments

I have just passed the 70-483 exam. The next one will be the 70-486. I thought that that would make me an app builder.

Microsoft Certified Solutions Developer: App Builder 2017

 

But that is (probably) not the case…

snip_20170131150257

Passing 70-486 would give me: “Microsoft® Certified Solutions Associate: Web Applications”

and after that, I am still required to get one of the electives. Because I passed the 70-345 and 70-355 too soon Crying face

So next stop: 70-486!

 

Good luck!

ps. will the Microsoft Certified Solutions Developer Universal Windows Platform become obsolete after march 2017?

Pin on pinterest Plus on Googleplus Post on LinkedIn

As you might have noticed, there is no Paste as XML option under Edit –> Paste Special in the menu when you are working on .net Core applications.

The reason is actually very simple. The current project type has no build in serialization support for XML.

I only realized it after reading this post from codecalculated.com. But it has been mentioned in the Asp.Net Standup before. 

However, I have a workaround available for those who have Visual Studio Code installed. You should have it on your machine! It is so fast, responsive and lightweight (and free).

Fire up Visual Studio Code and hit Ctrl+P and type: ext install smartpaste

snip_20161130105646

if you have it installed and reloaded Visual Studio Code you can invoke it with: Cltr + Shift + P and type: smart paste.

Select “Paste XML as JSON” (since xml to classes is not finished yet)

Copy the JSON output and switch to Visual Studio 2017 RC.

snip_20161130105859

You can now paste your JSON as Classes Smile

 

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn
0 Comments

This is my solution explorer:

solution-explorer

and this is my nuget package manager:

nuget

So The XmlSerializer is installed. Somehow the Newtonsoft.Json gives a yellow icon in the solution explorer. But no errors from that lib in the output window.

I thought that the nuget packagemanager or visual studio would auto restore all packages for me. Somehow it was fixed by manually running dotnet restore from the cli.

The whole tooling for .net core is still work in progress and I really liked working with preview 2 (1.0.1) in vs code with the project.json files.

Switching back to the csproj file makes it imho harder to work with vs code and makes using Visual Studio 2017 (community) almost required.

I really enjoyed working through the jonhilton tutorial for dotnet core.

But that does not work anymore, because 1.1 is out and project.json is gone.

I have used dotnet migrate to move from project.json to projectname.csproj and it returned zero errors/issues. But did not launch. No project was found according to msbuild. And after changing task.json it gave a lot of reference issues. So I started over in Visual Studio 2017 RC and have a lot more setup by default and less issues.

I see that the whole development of dotnet core is moving forward fast. But I really enjoyed the development experience with vs code and the jonhilton tutorial. I hope that it will come back, or that someone will make a similar tutorial for vs code with dotnet 1.1 and mvc (and kestrel, because vs2017 has iis express as default webserver)

Looking forward to all the new bits and pieces and will keep updating vs code (insider) and dotnet core.

I hope the suggestion of the manual dotnet restore helped someone.

 

good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn