Yeah I know its new year and i am back from quite some time. during these days i was learning things but could not able to make time to blog about it.
This year would like to write more on Azure and SQL 2017 with other Database technologies.
Things are changing with Cloud, RDBMS, NOSQL, Big Data, Data Scientist, Data science and AI.
Future will be different for DBA looks like:)
After SQL Server support on Linux Microsoft is not have another great enhancement where now Azure supports MySQL and PostgreSQL database technologies. this shows that no Microsoft is going to lead the industry by making themselves ready for tomorrow where Supporting Linux and Linux supported Database technologies(Open source) … Cool
so you name it and Microsoft delivers that. that the approach it looks like.
Azure is awarded as a best cloud support after AWS that a great achievement.
BI area Microsoft is leading the industry.
And The way SQL Server 2017 is designed when actually everyone start using it, I would say it will make a big difference. lets see……
I Know SQL Server 2005 is no longer in support by Microsoft, but Want to provide a solution for those who have legacy system and come across a issue where maintenance job failed in jobs and on maintenance plan history shows success but no task/subplans shown.
error code 0x80131500 (Failed to retrieve data for this request)…DTSER_FAILURE
This generally happens when you made changes in the databases(database offline) and other stuff or an old maintenance job.
For now I do not get the root cause for it but simple solution would be to create a new maintenance plan for faster resolution. i think its a BUG for SQL Server 2005.
As you know Microsoft has retrieve the data from Hadoop with by polybase and extended the R language to External language(R and Phython). now Microsoft is wanted to make sure that it has feasibility for all the environment whichever is available in the market. earlier I blog on MongoDB which is happening and favorable to developers for document store and containers concept, CosmosDB is the similar architecture of MongoDB for horizontal data storage , container and Document with the help of DocumentDB.
Microsoft has introduced many things recently(SQL 2016/17):
SQL Server on Linux
SQL Server – PolyBase (Hadoop Compatibility- data retrieval)
Azure SQL Server – CosmosDB – MongoDB
This indicates that Microsoft do not want to be isolated on Windows platform nor want to restrict to small scale… and Its been proved that Microsoft is doing great on this area… the only thing I believe is the SME for those new concepts which has been introduced unless we do not know how to manage it we may not be expert of doing it so.
Posted in Azure, Cloud, NoSQL, Others, sql 2016, SQL Server 2017, SQLonLinux
Tagged Azure, Cloud, NoSQL, SQL Server 2017, Whats New
Yes thats true, SQL Server New version will be release this year and call it “SQL Server 2017” where sql can also work on Windows, MacOS and Linux
SQL Server is running on Linux now with SQLPAL- SQL Platform Abstraction Layer(SQLPAL) -it will work as a virtual Windows server on Linux so I think now Microsoft should able to include things which we are doing on Windows Server.
on that note, Now vNext with CTP 1.4 Microsoft has introduce the SQL Server Agent functionality on vNext.
Yes that is true, now SQL Server is on Linux.
Download the public preview
I am learning it and would love to write more blogs soon.
In our earlier blog we discussed an introduction to MongoDB. so, how is MongoDB is into BigData, MongoDB has a concept called sharding with replication, so here using sharding it uses a cluster like configuration and data will be load-balance- equally distribute to multiple shard with the shard key.
so if we consider the HDFS- hadoop concept here unlike named node we have config server and shard is like data node. but here we have data is distributed to multiple shards but in hadoop system data is replicated to multiple data nodes. and MongoDB maintain the redundancy by using Replication.
Balancer makes sure that data is distruted equally to all the shards if data is not balanced balancer will run the processes at background and balance the data.
here shard key plays a very important role.
will write more on it later.