Code to view the partition table data. use Test_Tbl_Partition go /* -- find no.of partition table select object_schema_name(i.object_id) as [schema], object_name(i.object_id) as [object], i.name as [index], s.name as [partition_scheme] from sys.indexes i join sys.partition_schemes s on i.data_space_id = s.data_space_id */ go SELECT ISNULL(quotename(ix.name),'Heap') as IndexName ,ix.type_desc as type ,prt.partition_number ,case when ix.index_id < 2 then prt.rows else 0 END as Rows ,cast (rv.value as datetime2(7)) as [Upper_Boundary] ,prt.data_compression_desc ,ps.name as PartitionScheme ,pf.name as PartitionFunction ,fg.name as FilegroupName ,au.TotalMB ,au.UsedMB ,case when pf.boundary_value_on_right = 1 then 'less than value column' when pf.boundary_value_on_right is null then '' else 'less than or equal to value column' End as Comparison ,fg.name as FileGroup FROM…
-
-
Table Partition Microsoft SQL server part 1
What is table partitioning? Table partitioning is a way to divide a large table into smaller pieces as a partition logical unit. By default a table will be stored into single partition that is partition number 1. The data of partitioned tables and indexes divided into logical units that may be spread across more than one file and filegroup in case if we use file and filegroup method in the database creation, otherwise it will be stored into a single default MDF Primary file and filegroup. Having multiple filegroup or single file group is depends on the application requirement it is not going to do anything with table partition for…
-
The log scan number passed to log scan in database is not valid. This error may indicate data corruption
Database went into suspect mode database corruption One of our servers got migrated from one data center to other data center using third party tool called Zerto. After migration two databases went into suspect mode. Errors in the log: The log scan number (40359:103:2) passed to log scan in database <db name> is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup During undoing of a logged operation in database <db name> , an error occurred…
-
Login failed for user Reason: Token-based server access validation failed with an infrastructure error Login lacks Connect SQL permission.
Login failed for user Reason: Token-based server access validation failed with an infrastructure error Login lacks Connect SQL permission. Login failed for user ‘localhost\windows_user’. Reason: Token-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission. [CLIENT: <local machine>] Check you have permission to the user, generally we will have permission. Check you are able to access SSMS local & remote. Most of the case issue will be – Check how many group has deny permission, definitely your login will be one of in the group. For our case it was built in user group. SELECT sp.[name],sp.type_desc FROM sys.server_principals sp INNER JOIN sys.server_permissions PERM ON…
-
MSSQL Query running fast in production and slow in non-production
Query running fast in production and slow in non-production I have asked to look one of the queries that run fast in production and slow in non-production. Question asked – how long it took to complete the results. It is about 1.50 minutes in non-production, but in production it completed less than 5 seconds. Got the code and run myself in SSMS to compare the plan, since it will finish 1.50 minutes. It quickly showed estimated number of rows are totally different. This could be either out of stats or data skew. I just checked the last stats update and updated the stats that fixed the issue. You can…