Category Archives: SQL Server
Did you hear the news?
Microsoft is changing its Service Model for SQL Server and the major difference is that Service Packs will be no longer released starting on SQL Server 2017. However, this doesn’t mean that you no longer will have new features and product enhancements, rather than they will release new features and so on in Cumulative Updates.
Why are they doing this for SQL Server 2017? Well, in my personal opinion I believe that with major product versions being released almost every year or two years, they want to be faster in terms of releasing new fixes, launching new features and so on. Read the rest of this entry
I think many of us have not heard this, but recently (maybe not that recently) Microsoft made the SQL Server Docs available on GitHub under this link: https://github.com/MicrosoftDocs/sql-docs
Currently, if you navigate to any SQL Server Documentation and let’s say that you right now goes to this link: https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server in the right hand side of the window you will see this… Read the rest of this entry
I’m not sure if you guys know it, but on October 07th, 2017 we will have another amazing SQL Saturday 656 that it is taking place in Copenhagen, Denmark.
Surely, it will be an amazing day of learning and network from the Data Platform Experts that are coming from all places. So, if you are an IT person and is not quite sure yet on what do to on Oct, 7th, join this FREE event. You can get all the details from the home page.
Two things that are important to mention! Read the rest of this entry
In my first blog post about Python and SQL Server, I gave a very short introduction in how to actually connect and execute a simple query. Today I want to extend a bit on using Python and SQL Server.
As I described in the end of the previous post the ideal scenario is that you inherit the database connection from a single file and then use it whenever and anywhere you want. This makes your code to look cleaner and eliminate redundant work in case you need to change credentials or something else. For that I will show to you how to do it. Read the rest of this entry
I just wanted to do this quick blog post to give you a tip about a recent problem that I had in a SSIS Project. My scenario is the following.
Source Database Server: PostgreSQL
Target Database Server: SQL Server 2016
As you can see, I need to extract data from this PostgreSQL database and import in SQL Server. So far everything is working, but today I got this error of in one particular table: [OLE DB Destination ] Error: An error occurred while setting up a binding for the “MyColumnName” column. The binding status was “DT_NTEXT”. The data flow column type is “DBBINDSTATUS_UNSUPPORTEDCONVERSION”. The conversion from the OLE DB type of “DBTYPE_IUNKNOWN” to the destination column type of “DBTYPE_WVARCHAR” might not be supported by this provider. Read the rest of this entry
Lately I have been studying a bit of Python that I intend to use at work for some projects and also for learning a new language. I would recommend for you to also learn it, because as you know Python is coming to SQL Server 2017. The thing is that with Python you can use in your Machine Learning models, build Websites using some other frameworks such as: Django or Flask and even automate trivial tasks of your daily basis.
However, something that I know from the top of my head now is: Python was not designed in the first hand to deal with Microsoft SQL Server as a backend database. You don’t find lot’s of examples, the documentation sometimes is a bit misleading and errors and more errors that you cannot even imagine. If you search about Python + MySQL, Python + PostgreSQL, you will find lots of examples out there. I am not saying this is bad or anything, but it is just the way it is. Read the rest of this entry
I wanted to share something that I am doing this week at work. One of the applications that I support is generating a lot of transaction log in the database. Just to have an idea, we run Transaction Log backups every 30 minutes and I have backups over 100GB and sometimes 200GB. The difficult part of investigating what is generating that amount of log is because the databases involved are used by at least 3 different applications and streams. So, I remember that in the past I created a simple script that looks at this information in the database and then I may have more inputs of what is really generating that amount of log. Read the rest of this entry