Running software on Linux is supposed to be cheaper than Windows. After all, you don't need to pay for an OS license, right? I'm not sure I think the price of the OS is a determining factor, since it's a relatively low amount compared to the cost of the database license. I'm sure some of your feel differently, and I'd be happy to listen to your argument as to why the Linux is better on price.
In any case, Microsoft is looking to push the Linux version of SQL Server. For a limited time (until June 30, 2018), you can get 30% off the cost of a SQL Server license. They've also gotten the cost of SUSE Enterprise Server down to $0 for a year if you are a qualified customer. This does require an annual subscription, which I assume means Software Assurance. There's not a lot of information available on their page, and I assume you'd need to call Microsoft and go through the sales process.
It's an interesting offer. I wonder if this would really make a difference for some of you. For the purpose of a discussion, let's say you run an older version of SQL Server on Windows, like SQL 2000 or 2005. You want to upgrade, but your boss has been worried about costs. Now you see a 30% savings on Linux. Do you consider moving to a Linux OS instead of Windows? Let's assume you have some Linux resources inside the company, and so there isn't a large learning curve. Does 30% make enough of a difference do change the underlying platform? After all, for the post part, SQL Server is SQL Server.
What if you are a Linux shop already, and you have Oracle or DB2 in house. You're looking to move some software to a new system, or maybe develop new applications and SQL Server is being considered for cost savings. You've avoided it because it has required Windows in the past. Do you now consider SQL Server a more viable candidate as a relational database inside your environment?
When a SQL Server database is operating smoothly and performing well, there is no need to be particularly aware of the transaction log, beyond ensuring that every database has an appropriate backup regime and restore plan in place. When things go wrong, however, a DBA's reputation depends on a deeper understanding of the transaction log, both what it does, and how it works. More »
SQL Server T-SQL Recipes is an example-based guide to the Transact-SQL language that is at the core of SQL Server. This edition has been lightly updated for SQL Server 2014 and provides ready-to-implement solutions to common programming and database administration tasks. Learn to create databases, create in-memory tables and stored procedures, insert and update data, generate reports, secure your data, and more. Get your copy from Amazon today.
Yesterday's Question of the Day
(by Steve Jones):
I have database with some unbalanced file sizes in a filegroup. There are three files that are 10GB and one that is 2GB. I decide to remove the 2GB file. I run this:
DBCC SHRINKFILE(TheFirstFile, EMPTYFILE);
After doing this successfully, I decide that I should just change the file size of TheFirstFile to match the others. If I change the file size, will new data now go into all four files in a proportional amount?
Answer: No, this file is been marked as read-only
When DBCC SHRINKFILE (x, EMPTYFILE) completes, it marks the file as read only so no data is added to this empty file and you can delete it.
This procedure will find most fragmented and most accessed indexes server wide. and then rebuild or reorganize depending on your parameters.
So it will alter/list only the indexes which you will get the most benefit of fixing defragmentation.
Important Note : This procedure can create extensive IO operations. Please check first in DEV environment and beware that altering indexes can also create locks. That's why please use it with caution in PRD environments. Please try to exclude every unnecessary database name in WHERE clause and try to reduce the load.
Please create the stored procedure
Execute the procedure in debug mode first: EXEC sp_FlexibleReindex @Debug=1 this will only list the indexes sorted by most benefit
Please execute the procedure with the parameters that satisfy your needs
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.