Nice question.

From this we know that deleting records from the heap will not deallocate pages. Shriking will help to deallocate the pages from the heap ?

I know shrinking...

+1

Yes we can create Clustered Index on a non-unique and nullable column.

If the clustered index is not a unique index, SQL Server makes any duplicate keys unique by adding an...

Index has the limitation of 16 key columns, primary key can be either clustered or non-clustered. So it can also have only 16 columns. I guessed the answer as above.

🙂

Nice one!!! I guessed the answer with option 3 should be false.

Great !!!

I used distinct to avoid duplicates.

But I won't suggest that as well 🙂

This might help as well

;With CTE

As

(Select *, Count(1) Over (Partition By TagSetName) As rn From Ex)

Select a.ProjectName, a.WorkType, a.Status, a.TagSetName,a.TagValues from CTE a where rn =1

union

Select distinct a.ProjectName, a.WorkType,...

Nice question.

When we print the variables we can see the padded space in @a.

PRINT @a

PRINT @b-2

PRINT 'A:'+@A + 'B:'+...

Thanks

I have got in CTE

;with getMaxCourse AS

(Select cid,count(sid) over (partition by cid) Kount From enroll)

Select cid from getMaxCourse where Kount = (Select max(Kount) from getMaxCourse)

Nice Question and my guess is right today 🙂 !!!

Nice Question.. Thanks

Happy Valentine's Day !!!

Hi Andrew,

Can you share the link where you found the options.