View limitations in sql server Part 42

Поділитися
Вставка
  • Опубліковано 18 лис 2024

КОМЕНТАРІ • 25

  • @krzysztofs8535
    @krzysztofs8535 7 років тому +6

    your style of teaching in awesome!

  • @sravankumar1767
    @sravankumar1767 4 роки тому +1

    Way of explanation is Awesome

  • @bethtilley9168
    @bethtilley9168 9 років тому +5

    Well done! You are my favorite tutor in You Tube. Do you have tutorials for advance SQL server 2012?

  • @sweetmail52
    @sweetmail52 12 років тому +2

    you are superb tutor...!!!
    Thanx for sharing your knowledge...keep it up

  • @sravankumar1767
    @sravankumar1767 4 роки тому +2

    Nice explanation

  • @vasavisaikrupa6719
    @vasavisaikrupa6719 9 років тому +2

    Hello Venkat, your videos are very useful. At this time time i want to know why we are unable to use order by clause while creating view... Thank you

  • @rajunegi9011
    @rajunegi9011 2 роки тому +5

    Could you please also tell us the reason of these VIEW limitations, like:
    - Why SQL Server doesn't allow to pass a parameter to a VIEW?
    - Why we have to use TOP clause while using ORDER BY ?

    • @Shankar-zi3yk
      @Shankar-zi3yk 10 місяців тому

      answer for ur first question because it doesnt store data

  • @adityasamanta8621
    @adityasamanta8621 10 років тому

    You have covered Procedures, Functions, and View - I was wondering which should be used when ?

    • @SuperGojeto
      @SuperGojeto 8 років тому +6

      +Aditya Samanta I guess Views for allowing non technical or least tech persons (maybe also for tech persons) to query and display data, Functions for making calculations or similar things and Procedures to execute large no of queries at a time without needing to write thousands of lines of queries again and again.

  • @lordgaulo6520
    @lordgaulo6520 4 роки тому +2

    you should append a give a like message at the end of your videos I'm sure many people are watching the playlists like myself and we are forgetting to give it a like, I recommend at least once at the end of each video, because people like myself are most likely forgetting after the third video.

  • @malangraja5757
    @malangraja5757 3 роки тому +1

    Hi Sir
    Could you please post the tutorial about SQL Performance Tuning?

  • @seniortaco100
    @seniortaco100 11 років тому +1

    Nice video. Thank You.

  • @justinli19901027
    @justinli19901027 8 років тому +1

    pure awesomeness!

  • @sunilr2944
    @sunilr2944 12 років тому

    awesome explanation

  • @leonsomedina716
    @leonsomedina716 10 років тому +1

    Awesome!

  • @kiransurvase96
    @kiransurvase96 9 років тому +1

    Good Explanation Thanks...

  • @krismaly6300
    @krismaly6300 9 років тому +1

    Revisiting
    Thanks a lot

  • @maliksoft3675
    @maliksoft3675 7 років тому +1

    i don't know why those 2 dislikes the videos?

  • @santoshjaiswal9717
    @santoshjaiswal9717 4 роки тому

    I have one question,can anyone pls have a look :
    The inline table value function he created is based on the table, means the function is actually calling a table and not view @4:35

    • @thefrugalinvestor9392
      @thefrugalinvestor9392 2 роки тому

      Brother, he said we can use inline valued functions when we need to apply parameters
      For example, if we need only males so we can apply inline function instead of using view because view doesn't allow us to apply parameters.

    • @rajunegi9011
      @rajunegi9011 2 роки тому

      Inline table value function is the replacement of PARAMETERIZED view.

  • @stutitehri993
    @stutitehri993 10 років тому

    I guess views are not of much important

    • @sureshrajput5794
      @sureshrajput5794 9 років тому

      #Stuti# #Tehri# bro its imp when u wnt to give some limitations to outside users . so u can just create a view according to user needs and then u can grant tht view so he will b able to see nly those records which are stored by a view :)

    • @pcdispatch
      @pcdispatch 6 років тому

      Views are very useful. You can use them to create an abstraction between tables and the user. You can then make changes to the view without the need of changing user code. Also it is useful for complex queries and reuse.