Connect() is a yearly, Microsoft-hosted developer event that is broadcast live from New York City to developers worldwide.
The Connect(); 2017 Live Stream will begin at 9:45am US Eastern (15:45 Central Europe) with a pre-show and the Keynotes will start at 10:00am Eastern (16:00 CET) on November 15th and stream live 15th and 16th.
Watch the stream here:
Event website: http://connectevent.microsoft.com
They will be tweeting & posting from @VisualStudio @OpenAtMicrosoft @Azure and other handles using the hashtag #MSFTConnect.
External USB drives should be safely detached from Windows instead of just unplugging them from the computer. Most of us know that by now.
But sometimes a safe eject is not possible for no obvious reason. There are some weird situations when we think we closed all the programs that access the drive but there is still something in the background that prevents a safe eject. Here are a couple of tips that you can try the next time this happens to you:
It’s official: the next version of SQL Server, planned to be released this year, will be called SQL Server 2017. It is currently in the Community Technology Preview (CTP) 2.0 stage which is the first production-quality preview of the product.
Even though it’s coming just a year after SQL 2016, it’s bringing some game-changing features. Here are the highlights:
It’s quite easy to hit the PrintScreen key and capture the whole screen. But how do we quickly capture a part of the screen ? If you are using OneNote, there’s a very cool trick I want to share with you:
About two years ago I wrote my first blog post.
About a year ago I paused my blogging activity. That’s when I joined Microsoft…
Here’s a new feature that I like very much: Limiting exposure of sensitive data like user emails, phone numbers, addresses, credit card numbers and so on.
This feature has been available in the Azure SQL Database for a while and now it is included in the new SQL Server 2016 . So let’s see it in action…
Proper configuration of the TempDB system database is crucial for optimal performance of a SQL Server instances during heavy loads. The recommended strategy is to create multiple data files, one per CPU core (logical processor), but not more than 8. Those files should be equal in size and with the same autogrowth settings. In past, this had to be done manually after the initial installation of SQL Server so many instances went to production with default values. SQL Server 2016 allows the configuration of TempDB DURING the setup process and it also sets better default settings than ever before. Continue reading
It’s the first day of the year 2016 and I’m thinking about all the SQL events I attended in 2015.
My previous post was focused on controlling read operations. With the latest enhancements to the row-level security, it is now possible to restrict write operations as well. This feature is
currently available as a preview now generally available in Azure SQL Database V12. Let’s see how that works.
Row-Level Security (RLS) is a new feature of SQL Server 2016 and Azure SQL Database that enables data access control based on the users executing those queries: if a user isn’t authorized to access certain rows in a table then those rows are automatically filtered out by the database engine. This feature promises to simplify design and coding of applications, especially in complex multi-tenancy environments, as the access control logic is moved from the application to the database. In short, instead of writing queries like this:
CREATE VIEW vwInventory AS ... (implements security logic);
SELECT * FROM vwInventory WHERE isVisibleTo = 'Paul'
We write simple queries like this:
SELECT * FROM Inventory;
Isn’t that cool?