The Young DBA

Last month I got a chance to optimize some queries of a postgre sql database in my current organization. I was totally new to this database. SQL Server, mySQL, MongoDB, and now, postgres. I  never say a 'no' if some work related to database comes to me, and especially, if the database belongs to the RDBMS family, then, I can never say a 'no', as I am always keen to learn new and new trends. My thought for postgres was wrong earlier. I used to think that it is less popular than mySQL, but, I was wrong. When I started working on it, I found it much better mySQL in some scenarios, like - query optimization(using execution plan and statistics). Technically, Postgres is "better SQL" as it is more standardized. With better query planning, so that you can follow the relational model more closely if it suits you. Socially, MySQL has been very popular for a long time and many people are familiar with it. Postgres is neither owned by a major conglomerate with a qu

Sometime before I faced different kind of issue on one of staging SQL Server. I required to change the TCP port of an instance where multiple instance were running, I just open compmgmt.msc and connected SQLServer Configuration Manager , then I started receiving error : “ Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid class [0x80041010], SQL Server Cannot Connect to WMI Provider permissions or server is unreachable. ” This may caused by an issue with the compiled SQL Configuration Manager GUI’s communication with WMI. If we have multiple instance running on SQL Server on a single windows server or we have un-installed any instances then this kind of issues we may face to connect.

After-a-long time I got chance to work on MS-Access. MS-Access is very intresting database-application development tool. I like ms access a lot  becouse, this is the tool that helped me to turn into database in 2009.  Microsoft Access is a popular database management system (DBMS) from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical  user interface and software-development tools. Microsoft Access stores data in its own format based on the Access Jet Database Engine.  It can also import or link directly to data stored in other applications and databases. Now a days there are lots of changes in Access but basics are still the same.

Friends after a long time, I am writing a blog. I was away for last 3 months, due to one of the critical projects assigned to me from the client. Recently, we have moved a young elephant into a new and big room. Yes friends, elephant is a single Big-table of around 700+ GB data size and the room is of 5 TB storage with SQL Server 2014 version. Earlier, we had limited resources, older SQL version and huge data, which were altogether making system hell .

When we work with a single table in SQL Server, it is very easy to perform audit queries. But, while dealing with multiple tables of the same database, it becomes a very tedious job for new database developers. We need data from multiple sources(for example : all tables of a single database). As a newcomer to this field, i too got stuck in the same kind of queries, so, I have searched the web and have listed down a few queries that can help in retrieving data through audit queries. 

A MySQL event is a task that runs based on a predefined schedule therefore sometimes it is referred to as a scheduled event. MySQL event is also known as “temporal trigger” because it is triggered by time, not by table update like a trigger. A MySQL event is similar to a cron job in UNIX or a task scheduler in Windows. You can use MySQL events in many cases such as optimizing database tables, cleaning up logs, archiving data, or generate complex reports during off-peak time.

When we start developing a database, we have to use the most appropriate data types for all the columns to store data values of the respective tables in it. For dealing with the floating type data values, most of the times, we get confused about which data type to go for, as we have Float, Decimal and Double as well. I, myself, as a new DBA, got confused about the usage of the same. So, i have re-searched through some websites over internet and have concluded some facts about these data types' usage. i want to share my experience with all of you.

Avro schema generally used to define the data schema for a record's value. This schema describes the fields allowed in the value, along with their data types. We can apply a schema to the value portion of an Oracle NoSQL Database record using Avro bindings. These bindings are used to serialize values before writing them, and to deserialize values after reading them. The usage of these bindings requires our applications to use the Avro data format, which means that each stored value is associated with a schema. The use of Avro schemas allows serialized values to be stored in a very space-efficient binary format. Each value is stored without any metadata other than a small internal schema identifier, between 1 and 4 bytes in size. One such reference is stored per key-value pair. In this way, the serialized Avro data format is always associated with the schema used to serialize it, with minimal overhead. This association is made transparently to the application, and the internal sche

Difference between key-value stores and key-value pairs or Difference between  Key-value stores  and document db or Difference between Redias and mongoDb .   Key Values always Conf us ed me that's why i decided to share my some short of experience , In NoSQL Databases KV Pair and KV Stores are different. Event they are related to different database vendors too. Key-Value stores ; store keys value pairs  in buckets, exactly like a hash table data structure; where each key must be unique.  They are extremely fast for writing, and extremely fast for reading and updating. if you have the key.  They are slow on multiple updates and if you have to query the entire store.  You see Key-value stores used a lot as caching stores because of their fast reads. eg: Redis, Riak, memcached, Azure's tablestore, etc Document Stores ; store data in "documents", typically XML or JSON documents. They're typically schema-less, so each document can contain any data that you want