By default a single file group exists for SQL Server databases. It is primary and default file group for that database. However for better manageability and performance optimization we may be required to configure additional file groups for particular database. Data may be spread over multiple files in different file groups. SQL Server provides an option to change the default file group from primary file group to any other. Read here my article related to Using Multiple File groups for a Database and Changing the Default File group.
Computed columns are handy feature of SQL Server database design. Few months back i write an article related to basics of computed columns in SQL Server. Some readers furthers discussed about more flexibility in different scenarios. So click here to read my new article related to using computed columns with little enhancements for different requirements.
Foreign Key relationships are widely used in SQL Server database design. They provide numerous benefits. However there are some associated issues while applying update/delete statements on parent table .i.e. table with referenced primary key. SQL Server provides rules to manage the effect of operation on child records. It is important to know the use and effects of these rules. Read my recently published article about Understanding the update and delete rules for SQL Server Foreign Key Relationships.
A database in suspect state restricts access to data or settings. Data in suspect databases can not be pulled out nor you can perform recovery operations. In such cases, no matter the problem is due to any corrupt data page or log file, recovery is a night mare. SQL Server 2005 has introduced a very useful state for working with suspect databases. You can set the suspect database to emergency state and then exploit the wide range of operations on data and settings.
SQL Server agent job schedules may be shared among multiple jobs. Jobs and schedules have a very flexible relation among them. Here is my article about aspects of sharing a schedule among multiple jobs. Click here to Read the article on MSSQLTips.com
Recently i explored a wonderful option provided in SQL Server Management Studio. SSMS allows to generate script for any operation performed through its GUI. It is awesome and provides you a comprehensive and authentic T-SQL code reference. You may save the GUI tasks performed in form of .sql files. Such code may be reused in daily tasks or scheduled jobs.
Click here to read my article for details of using this feature of SSMS.