このポストは、8 月 25 日に投稿した SQL Server AlwaysOn Template in Microsoft Azure Portal Gallery の翻訳です。
現在プレビュー段階にある Microsoft Azure ポータルのギャラリーに、新しいテンプレートが追加されました。追加されたのは SQL Server 2014 AlwaysOn テンプレートで、これを使用することで SQL Server AlwaysOn 可用性グループの作成を自動化し、セットアップ作業をバックグラウンドで処理できるようになります。Scott Guthrie が先日投稿したブログ記事 (英語) (翻訳: NAOKI SATO ブログ: Azure: 新しいDocumentDB NoSQLサービス、新しいSearchサービス、新しいSQL Server AlwaysOn VMテンプレートなど) では、このテンプレートのことを他の便利な機能と併せて紹介しています。
AlwaysOn テンプレートで基本的な設定 (または既定値) を選択すると、ホスト名のプレフィックス、可用性グループ名、オプションのリスナー名、VM 料金レベル (グループ参加者と監視 VM 用)、サービス アカウント/パスワードといった高レベルのオプションが指定されます。複雑な作業はすべてこのテンプレートで処理され、一連の VM の作成が完了し、以下のスクリーンショットのように接続された状態となります。
これならすぐにセットアップを完了して使用し始めることができます。AlwaysOn 可用性グループを Azure で実行する方法や新しいテンプレートの詳細については、SQL サーバーのブログ サイトの「Microsoft Azure ポータルのギャラリーで SQL Server AlwaysOn テンプレートを提供開始 (英語)」をご覧ください。
Application Insights team identified issue in data streaming services (around 00:50 8/30/2014 UTC) that caused unhealthy state in system. This issue has been mitigated and our monitoring is green. All the services are running as expected. We confirmed that there was no data loss during the impacted window (00:50 till 02:40). However during time time some users might have seen data latency for approx. 2 hours. We will closely monitor this space and provide an update this blog if there is re-occurrence.
We apologize for any inconvenience.
-Application Insights Service Delivery Team
Logo is a programming language that somehow involves a turtle. Imagine a turtle on a large piece of paper on the floor. The turtle has a pen. You can command the turtle to go forward, turn right, then repeat 4 times to draw a square. The last time I wrote about Logo (in 2006) I hadn’t read the current Wikipedia article on it, where it says Logo was invented at BB&N. I was surprised, because I too worked at BBN, in the early 80’s, designing computer systems to analyze sounds, writing convolutions…(read more)
There are two small tools in Windows which saved my day multiple times. I didn’t bother to write a blog post since I thought that it was not worth it but the two tools got me out of a big problem today (again). To appreciate the two tools I decided to write it down briefly.
With any further ado let me introduce them as below. The nice thing is that they are in the box.
Takeown.exe – take ownership of files/directories
Cacls.exe – change ACLs of files/directories
My case today
My system hanged when I did a certain operation which unfortunately I need to do regularly. This was very annoying since I couldn’t work effectively. To fix it I need to copy a system file to a system folder. This is not an easy operation. You will get access denied by default. If you don’t believe it open the folder c:windowswinsxs (replace c: with your system drive) try to create a new file/folder or delete anything or copy anything there.
What I did is very simple. I just ran the below command to take control of that folder and copied the file there. Then I could solve the problem.
takeown /f [foldername]
cacls [foldername] /G [username]:F
If you run into any problem related to access denied when doing any file/directory access operation feel free to give these two cute tools a try. It won’t disappoint you.
When you add/configure and publish a package in App-V, the primary file assets and source registry hives are stored in the package cache location. It defaults to %PROGRAMDATA%App-V. The package cache will store packages in a <PACKAGE_GUID><VERSION_GUID> directory structure for each package added to the machine regardless of targeting. This package cache will exist for the purposes of marking key assets in both stream-to-disk scenarios in stream-to-memory (Shared Content Store) scenarios…(read more)
Kevin Remde and Keith Mayer continue our series on “ Modernizing Your Infrastructure with Hybrid Cloud ” and in today’s episode they discuss various options for networking. Tune in as they go in depth on what options are available for hybrid cloud networking …read more…(read more)
In my previous Construct 2 tutorials, we covered a top-down shooter and a flappy bird clone, derived from Scirra.com tutorials. In the following presentation, you’ll learn how to make simple improvements to Flapping Bird. High score, with WebStorage …read more…(read more)
We will be shipping an update to Visual Studio Online. We are planning on having maintenance windows from Tuesday, 2 September, 19:00 UTC through Friday, 5 September, 23:00 UTC.
In this deployment, we will the roll out the next phase of updates to enable Work Item based Test Plans and Test Suites on Visual Studio Online. As you might have noticed, Test Plan and Test Suite work items have already been created, however these are not yet ready for consumption – kindly note that these work items should not be modified or destroyed. We will explicitly let you know when work item based Test Plans and Test Suites are ready for use.
On Saturday, 6 September, after this deployment is complete, there will be a maintenance activity to update the existing Test Plan and Test Suite IDs with the corresponding work item IDs. During this update, the Test Management service will be unavailable and the interruption will last for few seconds to few minutes, depending on size of your account. Please update any bookmarks that contain Test Plan or Test Suite IDs after this update, because the Test Plan and Test Suite IDs will change. This update is scheduled on a weekend – Saturday, 6th September 2014 – to ensure minimal impact to your account users.
My application starts slowly, I want to preload it to avoid that problem. Should I be worried?
Well, in short, there are lots of concerns. Preloading things you may or may not need is a great way to waste a ton of memory and generally make the system less usable overall.
I’m often told that that the answer to a performance problem is to simply preload the slow stuff… unfortunately that doesn’t work as a general solution if everyone does it. It’s classic “improve the benchmark” thinking.
When developing for Windows you have to think about all kinds of scenarios, such as the case where there are several hundred users trying to share a server each with their own user session. Your application might also need to run in a very memory constrained environments like a small tablet or some such – you do not want to be loading extra stuff in those situations.
The way to make a system responsive is to KEEP IT SIMPLE. If you don’t do that, then it won’t matter that you’ve preloaded it — when the user actually gets around to starting the thing in a real world situation, you will find that it has already been swapped out to try to reclaim some of the memory that was consumed by preloading it. So you will pay for all the page faults to bring it back, which is probably as slow as starting the thing in the first place. In short, you will have accomplished nothing other than using a bunch of memory you didn’t really need.
Preloading in a general purpose environment is, pretty much a terrible practice. Instead, pay for what you need when you need it and keep your needs modest. You only have to look at the tray at bottom right on your screen full of software that was so sure it was vitally important to you that it insisted on loading at boot time to see how badly early loading scales up.
Adding fuel to this already bonfire-sized problem is this simple truth: any application preloading itself competes with the system trying to do the very same thing. Windows has long included powerful features to detect the things you actually use and get them into the disk cache before you actually use them, whether they are code or data. Forcing your code and data to be loaded is just as likely to create more work evicting the unnecessary bits from memory to make room for something immediately necessary, whereas doing nothing would have resulted in ready-to-go bits if the application is commonly used with no effort on your part.
Bottom line, preloading is often a cop out. Better to un-bloat.