To create a gap, delete employee record from the #Employee table with id = 2 by the following script: RESULT: Now let us run the example 1’s approach 1 and 2 script on #Employee table which is having gap in the Id column value (i.e. From the above result it is clear that the example 1’s approach 1 and 2 script will not work in the scenarios where we have gap in the looping tables column values.This problem can solved in multiple ways, below are two such example approaches. Approach 1: Looping through table records where looping column has gaps in the value RESULT: Now let us run the example 2’s approach 1 and 2 script on #Employee table which is having duplicate Id column values (i.e.there are two records with with Id column value as 1) From the above result it is clear that the example 2’s approach 1 and 2 script will not work in the scenarios where we have duplicates in the looping column.Here only one record of the employee with id =1 is displayed and other record is skipped.For instance, you can add or remove features as needed.By using SQL Server to build your inventory, you acquire the most compatibility and you don’t incur extra cost, installation, or resource burden.I think filegroups should be created based on these criteria: a) Is it read-only data?
I will also explain why this particular item is important and make any notes about version or usage as necessary. The criticality of each one of these depends on your particular environment so I will leave that to you as a DBA to decide which ones should have a higher priority. Suddenly the DBA is left with multiple TBs and all on a single PRIMARY filegroup.
When it comes to creating a SQL Server inventory, you can either buy a commercial product or build your own solution.
There are several benefits to building your own solution.
b) Does the data in the filegroup support a specific set of application functionality?
In this case, you can think of the scenario of doing a piecemeal restore.
Use the following tables to determine which features are supported by the various editions of Microsoft SQL Server 2005.