Translate

Monday, December 9, 2019

Encryption, Decisive Factor to lose the WWII

Germany and Japan were gaining momentum to win world war II and concur the world. Some crucial decisions have changed the complexity of the game upside down.
Until late 1942, the United States was not in the war as an active participant, though they were indirectly supporting their allays. In late 1941, Japan decided to give them a run by attacking Pearl Habour so that Japan can expand its control in Asia to Pacific whereas German is extending its powers through Europe. Japan wanted to destroy US Aircraft carriers so that they can get control of the pacific. However, on that day aircraft carriers were not in the port. After the Pearl Habour attack, the US wanted to give it back to Japan by attacking Tokoyo which they did successfully.

Image result for pearl harbour attack
Pearl Harbor Attack: Reference www.atomicheritage.org

Then Japan decided that they have to destroy the aircraft carrier which was escaped during the last attack. Japanese admiral, Yamamoto planed for a trap by attacking Midway island which is somewhat mid between Japan and the USA. Yamamoto divided his troops into three. First troops have to attack the bases in Midway, while his air troops will destroy the US aircraft carriers which will come rescue.

But,
this plan was de-coded by the US naval intelligence in Pearl Harbour. So the USA moved his troops close to the Midway way before the arrival of Japan's troops. Also, they had another set of troops waiting for Japan's arrivals.

Though the Japanese are more superior than the US naval troops, they were able to withstand the Japan attack, mainly due to the fact that the US was able to decode the encrypted messages of Japan communication.







Tuesday, September 17, 2019

Migrating On-Premises Microsoft SQL Server Business Intelligence Solution to Azure

Some organizations are looking at the possibility of migrating their Microsoft Business Intelligence solutions to the cloud due to cost-effectiveness, easier maintenance, scalability, etc. However, they are running current solutions on-premises which have been servicing their stakeholders for years. Because of this, with the cost factor and the time factor, it might not be feasible to start a new solution from scratch. Although they would like to lift and shift the existing solution to the cloud as-is, there are a lot of issues with that migration. Mainly, some of the existing features may not be compatible with the cloud. This article looks at how on-premises Microsoft Business Intelligence solutions can be migrated to an Azure environment.

Wednesday, August 28, 2019

SQL Server ALTER TABLE ADD Column overview


In this article, we will explore SQL Server ALTER TABLE ADD Column statements to add column(s) to an existing table. We will also understand the impact of adding a column with a default value and adding and updating the column with a value later on larger tables.

Naive Bayes Prediction in SQL Server

This is the second article of the data mining series.
https://www.sqlshack.com/naive-bayes-prediction-in-sql-server/

Tuesday, August 27, 2019

SQL Server 2019 Reporting Services RC1 now available - here's all that's new

Last year, Microsoft announced SQL Server 2019, its new database management system (DBMS) that helps manage both relational and non-relational databases through a common service. It runs on-premise, in the cloud, and on Azure Stack as well.

Read more from https://www.neowin.net/news/sql-server-2019-reporting-services-rc1-now-available---heres-all-thats-new

Wednesday, July 31, 2019

Introduction to SQL Server Data Mining

Prediction, is it a new thing for you? You won’t believe you are predicting from the bed to the office and to back to the bed. Just imagine, you have a meeting at 9 AM at the office. If you are using public transport, you need to predict at what time you have to leave so that you can reach the office for the meeting on time. Time may vary by considering the time and the day of the week, and the traffic condition etc. Before you leave your home, you might predict whether it will rain today and you might want to take an umbrella or necessary clothes with you. If you are using your vehicle then the prediction time would be different. If so, you don’t need to worry about the rain but you need to consider the fuel level you need to have to reach to the office. By looking at this simple example, you will understand how critical it is to predict and you understand that all these predictions are done with your experience but not by any scientific method.

Read full article https://www.sqlshack.com/introduction-to-sql-server-data-mining/

Monitoring SQL Server Analysis Services with Extended Events

Monitoring is an essential aspect in any system and it is an important factor in SQL Server Analysis Services as well. Monitoring will help troubleshoot, audit operations and sometimes monitoring is needed to support various standards and legislation. SQL Server Analysis Services (SSAS) is an OLAP tool used for analysis of data and in many cases SSAS multidimensional cubes and tabular models contain data from many sources and therefore it might be essential to audit who is accessing what. Also, when there are performance issues in SSAS, monitoring needs to be enabled. This article discusses what options SQL Server provides to enable monitoring for SSAS.

Read this article https://www.mssqltips.com/sqlservertip/6121/monitoring-sql-server-analysis-services-with-extended-events/

Monday, June 3, 2019

Windows And SQL Server 2008 And 2008 R2 End Of Life


Windows Server 2008/2008 R2 and SQL Server 2008/2008 R2 are on their extended support phase now. July 8, 2019 for SQL Server 2008/2008  R2 and January 14, 2020 for Windows Server 2008/2008 are the end-of-life dates. Once you hit these dates, you will essentially be running those machines at your own risk in this bloated age of cyber attacks. 

Following are the options you have
Path 1:  The first path is the traditional evolutionary path of upgrading to a newer version of Windows Server and SQL Server. 

Path 2:  If you do not want to upgrade to the latest server versions—don’t worry—Microsoft has you covered. Microsoft recently announced a few options for those who want to continue on Windows Server 2008/2008 R2 and SQL 2008/2008 R2. To save money, you could simply move your Windows Server 2008/2008 R2 and SQL 2008/2008 R2 to Azure by using the Azure Hybrid Use Benefit. The only cost you would incur would be computed and infrastructure.

Read more at https://community.connection.com/windows-sql-server-2008-2008-r2-end-life-coming-soon-now/



Monday, April 29, 2019

SQL Server Analysis Services SSAS Hardware Configuration Recommendations

SQL Server Analysis Service (SSAS) is a different service for Microsoft SQL Server compared to the database engine service. Therefore, hardware configurations for SSAS need to be addressed differently.  What are the best practices?

Tuesday, March 19, 2019

SSRS Migration from SQL Server 2008 R2 to SQL Server 2017

As you are aware SQL Server 2008 R2 Microsoft support coming close to a shutdown, now people are starting to move to higher versions. 

This client wants to move its 800+ SSRS from SQL Server 2008 R2. Followings are learnings from the exercise.

1. SQL Server 2017 SSRS does not come as a single bundle of SQL Server. This means that you need to install SSRS as a separate installation. 

2. Though there are several ways of SSRS upgrade, ReportsServer database backup and restore was chosen as the method. In this, it is important to note that ReportServerTemp database also needs to be restored along with the ReportServer. SSRS service should be stopped before the restoring and with the restart of SSRS, SSRS services are upgraded automatically. Also, subscriptions schedules will be created as well. 

Do you think, you have completed your work. NOPE. still, a few touches are needed.

3. Authentications will not be transferred as a security measure. Therefore, you need to configure all of your data sources. If you have not managed your data sources carefully like this client, you will be coping and pasting connection strings, user names and password for one million times. 

4. If you have set up subscriptions for reports then there are few more things to be done. In standard subscriptions with excel, in the SQL Server 2008 R2 it will be configured as Excel 2003. This will be moved to that new version as it is, but will not work. It has to be changed to Excel. 

5. If you think that it is a tedious task in standard subscription, hold on for a second. There is more to come. In the case of Data-Driven Subscription, all the Excel file types are changed to MHTL Archive. Well, something little difficult to understand but that is how it is 

Sunday, March 17, 2019

SQL Server Migration Assistant (SSMA) v8.1

SQL Server Migration Assistant (SSMA) for Oracle, MySQL, SAP ASE (formerly SAP Sybase ASE), DB2, and Access allows users to convert a database schema to a Microsoft SQL Server schema, upload the schema, and then migrate data to the target SQL Server (see below for supported versions).


Monday, March 4, 2019

Recover from a Data Disaster – Point in Time Recovery Method

This is a fantastic feature in databases but you will not realize how valuable this until you come across this situation. Before describing these features, let us first look at two cases. Incidentally, these two incidents occurred in one organization and moreover for one database but at different times.

Incident #1:  A developer was connected to both production and development instances of databases from one SQL Server Management Studio (SSMS) instance. If you have work with SSMS, you would understand how risky this is. If not, this incident tells you how risky it is. The DBA thinking that she is working on the developer instance has deleted data in a customer table in Production.

Incident #2: In the same organization, they decided to increase the column length to 50 from 15. This column is a critical column to the business. They increased the size of the column using the design view from a table. Guess what, before typing the 0, after removing the 1 the user has saved the designed, which had resulted in truncation of the table column to 5 from 15 with a data loss.

Action: In both cases, we were to help. The first question was “What is the recovery model?” if it is Simple, then nothing that we could do as Simple recovery model does not keep the transaction log history and nothing can be recovered. In these scenarios, the recovery model is Full means that we can recover data to a point of time. In this mechanism, we can recover to a given time. So, we got the full back up of the database and restored to a different database instance with the recovery option on. Then we got a log backup and restored on top of the previously restored database with specifying a time which is just before the disaster recovery. After the database is restored fully, customer table and the other tables were transferred to the production database.

Lesson Learnt:
·         Never connect to multiple databases instances from SSMS. Especially, with production and other database instances.
·         Never use a designer, to modify database schema. Always use scripting for schema design changes.
·         Always, use the Full recovery model for production.

Reference:

https://www.sqlshack.com/point-in-time-recovery-with-sql-server/


PN: Customer identity is hidden and will not be disclosed as per the policy. However, tried to expose technical approaches and tasks.

Saturday, January 26, 2019

Infrastructure Planning for a SQL Server Data Warehouse

A SQL Server data warehouse has its own characteristics and behavioral properties which makes a data warehouse unique. In this sense, a data warehouse infrastructure needs to be planned differently to that of a standard SQL Server OLTP database system.  In this tip we look at some things you should think about when planning for a data warehouse.

Read more at https://www.mssqltips.com/sqlservertip/5872/infrastructure-planning-for-a-sql-server-data-warehouse/