Learning is a journey and that is something I love to keep in mind. Even after being so many years in the industry, I don’t stop learning from peers and people around me. This is the best way I can get better at something. I have been writing about the comparisons working with Oracle and SQL Server in the past and I personally thought this was a great way to learn something new by understanding the concepts of something that we always know. The learning is easy when we are able to make an analogy or metaphor as part of our learning. Do you guys ever use a similar approach while learning something that is completely new in your day-today life? Let us learn about Logical Architecture today.
SQL SERVER – FIX: SQL Profiler Error – Cannot Retrieve Trace Definition for SQL Server Version
As soon as I opened profiler and clicked on “connect” button, I was welcomed with below the message box. This is one of the funniest error message which I have seen from long time. There is no message!!! Let us see how to fix SQL Profiler Error.
Hitting OK on above, came to below message.
The version shown in the message 13.0.900 is the version of my SQL instance (SQL Server 2016 CTP) on which I was connecting. Here is the text of the second error message.
SQL SERVER – Data Lineage Tracking in ETL Processes – Notes from the Field #124
[Notes from Pinal]: Everybody knows about ETL Processes. It is a simple process where data is extracted, transformed and loaded into an application or database. However, still today, not many people know about how to do data lineage tracking in ETL processes.
SQL SERVER – Unable to Start SQL Server – TDSSNIClient Initialization Failed with error 0xd
As a part of my passion, I do visit the forums and try to help. I contacted him personally via email and found an interesting situation. So, sharing it via the blog. I saw below post in a public forum about TDSSNIClient Initialization Failed.
Hi Experts,
I am not able to start the SQL Server service. Getting below error while starting SQL via configuration manager.
SQL SERVER – Error Msg 5042, Level 16 – The File ‘tempdev02’ Cannot be Removed Because it is Not Empty
As a SQL Server DBA you would know that sometimes it is possible to make mistakes with the database. Few of the time it can be corrected. Out of them, some are easy and some are difficult. I was running out of space on my VM and I started hunting for a bigger file on my machine. It was not difficult to find and recall that I added some files to the TempDB database while doing some testing. Here is the command to get details about the database file, which gave me Error Msg 5042.
SQL SERVER – FIX: Setup Was Not Able to Access Domain
One of my clients approached me to provide assistance in performance tuning – which is my bread and butter these days. Often once you get into an engagement, they try to maximize the time they get with me. While doing the tuning exercise, the DBA had a side question during the call. Let us learn about how setup is not able to access domain.
PowerShell Script – Backup Every Database In SQL Server
Using scripts can be a powerful way to automate things that a GUI will fail in many cases. I was working with a client who wanted to write a PowerShell script that would help him automate his backups. This is a pretty simple requirement that can be easily achieved using SMO as shown below in my scripts. I have been using these scripts for a number of years at various places. Let us see how we can backup every database in SQL Server