You need to implement a high availability solution for one of your SQL Server databases, but you’re not sure of which option to implement to satisfy your company’s needs. Check out this tip to learn about the five native SQL Server High Availability options:
While working on different database projects I usually find it very necessary to perform a data sizing exercise on all tables focusing mostly on the number of rows in order to determine a growth factor of each table. This kind of information is useful in performing long term planning of growth and scalability of the data that we are managing.
Out of an exercise like this one we can also determine future needs for data archiving.
Continue reading DATA sizing or SQL Server Rowcount without doing a table scan
Scenario proposal
When you install SQL Server the path for the installation is generally something such as the following: C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL.
In this directory there are also folders for your DATA files and also your BACKUP files. Within SQL Server Management Studio you have the ability to change the default location for your Data and Log files for all new databases, but you can not change the default directory for your backups.
Is it possible to change the default directory for backups, so it does not need to be specified each time I run a backup?
To determine what edition of Microsoft Sql Server you have installed you have to start Sql Server Management Studio and run the following query : Continue reading How to determine what edition Microsoft Sql Server you have installed
It is commonly known that you should not use SELECT * when you are writing a query.
Most of the times, we only need a some of the columns that a table has and we should retrieve only those columns.
This are some of the disadvantages of using Select * :
Continue reading How to avoid Select *