Database user and programming tips
On September 24th Microsoft released the first Community Technical Preview for SQL Server 2019, which was CTP2.0. At the same time Microsoft pushed out a new preview for SQL Server Management Studio (SSMS) known as version 18. Now is the time to download this new preview!
Microsoft announced the release or CTP 2.1 for SQL Server 2019. This is the second CTP released for SQL Server 2019, and it has lots of new exciting features, like " UDF inlining". Read on to find out more!
If you are not managing the transaction log space used by a database, the transaction log might grow uncontrollably. With SQL Server 2017 there is a new dynamic management function (DMF) that exposes statistical information about a database transaction log. One of the things you can do with the information returned from this DMF is to determine how full a database transaction log file is.
On Monday, Sep 24, 2018, at the Ignite 2018 conference, Microsoft announced the first public preview of SQL Server 2019 (community technical preview (CTP) release of SQL Server 2.0).This new release of SQL Server is packed with many new features to improve performance, integrate your increasing volumes of corporate data, beef up security, and more.
Have ever tried to debug a chunk of TSQL code (like a stored procedure) and found yourself trying to figure out which TSQL statement is at a particular line number? By default, SQL Server Management Studio (SSMS) doesn’t display numbers. But that is only the default, you can change it.
There are times when you might need to look at your SQL Server data in hexadecimal format. Occasionally some string data will contain unprintable characters, which can cause downstream problems, if not detected and removed. Read on to learn how to display and remove unprintable hexadecimal characters from SQL Server data.
When you are setting up a new SQL Server machine you need to determine how big you should make tempdb. To make sure you size tempdb appropriately you should monitor the tempdb space usage. If there are autogrowth events occurring after you have recycled SQL Server than you might want to increase the size of your tempdb data files. If tempdb never uses most of the tempdb space, then you might want to consider decreasing the size of tempdb.
There may be a time when you want to turn off transparent data encryption on one of your TDE enabled databases. In this tip, Greg Larsen shows you how simple it is to remove Transparent Data Encryption.
How many times have you had a programmer come to you and say they want you (the DBA) to restore their database to sometime prior to when they accidentally corrupted it? If you are doing FULL transaction logging you can do a point in time recovery to restore the database to just prior to when the corruption occurred. But in order to do that you need to know exactly when the programmer corrupted the data, which in a lot of cases is not known down to the second.
We all know that you should try to size tempdb appropriately, so it doesn’t need to autogrow shortly after starting up SQL Server. It isn’t always easy to do this. Therefore, when you first implement a new server and/or add new databases you should monitor the autogrowth events on tempdb. By monitoring the autogrowth events you can easily determine if you have sized tempdb appropriately.
When a database grows to the MAXSIZE the database will not grow anymore and if someone tries to add more rows they will get an error saying the database is full. Greg Larsen shows you how to find all database files that have their max_size set.
We all know indexes are important for improving your query performance, but to store and maintain indexes SQL Server requires disk space and compute resources. If you have indexes that are not being used, they are costing you valuable resources and causing your update statements to run longer. Those updates run longer because they have to maintain those unused indexes. If your application is not using an index, then there is no value in having that index. Read on to learn more.
Do all of your tables contain clustered indexes? Some say every table should have a clustered index. Greg Larsen shares a simple script to identify those tables in your database that don’t have a clustered index.
Why are you dropping and recreating your indexes, when you could just disable and then rebuild them? By disabling an index, you have basically turned off the index, but have allowed SQL Server to retain the index definition in the database metadata. If you want the index back all you need to do is rebuild the index.
By looking at a query execution plan, you can determine which steps are used to resolve the query. But what if you just want to find out what the query plans are for only the queries that are currently running?