Wow coming right on time as usually, looking forward for the next video about t-sql. When you write a stored procedure what should you write and why in every stored procedure things like on error rollback = true or something like that so it would run smoothly and safely on the production without timeouts. Now because I am doing everything locally everything works great but already thinking few steps ahead of how to set up stored procedures for the production. Hoping that this question can be answered in one of the next videos.
I agree with the comment about entity framework. Regardless of the data access tool - ie Entity Framework - you need to know the execution plans it will use or your performance will take a hit, especially on larger databases.
I realize this was a year ago but your reference to highlighting code to run and being careful with delete statements. I feel much better that you pointed that out ; as that was one of my worst memories starting out 15+ years ago. I had a Delete statement with a where stated. But a sensitive mouse and on my way to the Execute button I accidently RE-highlighted the script WITHOUT the Where and continued on to the Execute button, all in one motion. My team never heard a mouth like that or since, lol.
Hey there, god bless your efforts. i have a simple enquiry as a newbie. Does a cursor keep track only of the records in the result set or can it return to the original table? Thanks a lot.
Is attaching a database (via SSMS) to an existing visual studio proj (e.g. .NET Core Web API) a reliable way to have your table data transfer to other environments?
Sure, you can do MSSQL locally. In development, you can use Microsoft SQL Server Developer Edition for free on your machine (it is not allowed to be used in production). You have the option of running it locally or running SQL in Azure (or other hosts). It is up to you (although Azure is probably the cheapest option).
Sorry guys, but @min 42, why we need to use sanitized data? what des that mean? I understand the point of testing on much bigger DataSet, but I don't understand what is Sanitized data, searching online also says it's a cleaned data from some special chars, so I don't really understand why use sanitized data in this case.
Sanitized data in this context ("a sanitized version of your production database") means that you create a copy of your production database that you can use as a development database. Part of that process is removing or changing sensitive data. For instance, maybe you have a list of email addresses. You wouldn't want that to be the real list, since that would expose those records to people who shouldn't have access to them and since you don't have as strict of protections on your development database. So, you would change each email address to be something else. My personal preference in this specific case is to change any email to the user's first name dot last name at my test domain name. So John.Doe@test.iamtimcorey.com or something like that. To do this safely, though, you might also have already changed the person's last name as well.
@@IAmTimCorey I was following a tutorial for setting up api to connect a website and a sql database and the guy had a GUI interface for posting queries and everything to the database but the system just seemed to make the command line available or else seemed encourage going through Azure. I was trying to just follow the instructions explicitly so that I had a problem, then I could compare his Git repository commits to my own. I don't know if I emtered anything wrong, but all of my web searches and my understanding of the documentation pretty much seems like you have to either do command line or else go through Azure.
It's a lot to explain, but I figured out why the application kept closing as soon as I went to open it... it needed to be "repaired" and the repair failed the first time.
Have to admit, not watched the video (yet) as I use SSMS v18 daily, the one thing I hate is they removed the run in debug and breakpoints from SSMS. WHY! Have they brought it back for v19, doubt it? Tim, maybe a video about doing SQL stuff and debugging in Visual Studio (unless you have one already). Edit, NVM -- found you already have one -- ua-cam.com/video/ijDcHGxyqE4/v-deo.html
I have a question. you said a business would use a paid version of sql server. I've been in businesses where they were able to use sql server express and it worked fine. Which was great because there was one job where if the express version was not available, then i would have been out of luck because i only got paid 40 to 50 dollars a month and could not afford to pay out of pocket and the business would not be able to afford it either. I would think in most cases, sql server express is the best. i do know if the database size was too large, then they would be forced to pay a lot more for a paid version. the sql server developer version seems useless because of the restrictions.
I did say Express can be used in production. As for Developer Edition being useless because of the restrictions, that’s absurd. It is just the opposite. Instead of needing to pay a licensing fee to have a version of SQL on your development machine that mirrors what you use in production, you can use a free version. Mirroring production in development is important so that you can experience the same features that your production app has. Don’t complain about what you get for free.
I address this in the video. Both pronunciations are correct. Please stop trying to force one way. The original product was named Sequel (spelled that way). Microsoft people at all levels, including the product owners, say both even in the same video.
You should have at least mentioned that "sa" is system admin, "dbo" is database object, it's schema not owner. Maybe you should have mentioned the schema existence at least - access rights can be configured etc. The second part of the video sounds improvised and boring because it shows almost nothing. You used to have very informative videos with every unknown detail explained but this one isn't one of them.
I did mention that sa was the system administrator, I did mention that dbo stood for database owner (not object), I did mention that it was a schema, and that there were other options but in small databases, dbo was commonly the only one used. It sounds like you didn’t really watch the video.
Awesome, Tim! Keep up with SSMS intermediate to advanced videos! 😁
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
Been using SSMS for years... but learned a few things. Yet another awesome video.
Thanks!
Wow coming right on time as usually, looking forward for the next video about t-sql. When you write a stored procedure what should you write and why in every stored procedure things like
on error rollback = true or something like that so it would run smoothly and safely on the production without timeouts. Now because I am doing everything locally everything works great but already thinking few steps ahead of how to set up stored procedures for the production. Hoping that this question can be answered in one of the next videos.
I agree with the comment about entity framework. Regardless of the data access tool - ie Entity Framework - you need to know the execution plans it will use or your performance will take a hit, especially on larger databases.
Thanks for sharing.
I realize this was a year ago but your reference to highlighting code to run and being careful with delete statements. I feel much better that you pointed that out ; as that was one of my worst memories starting out 15+ years ago. I had a Delete statement with a where stated. But a sensitive mouse and on my way to the Execute button I accidently RE-highlighted the script WITHOUT the Where and continued on to the Execute button, all in one motion. My team never heard a mouth like that or since, lol.
Yep, we've all made similar mistakes.
Thanks great introduction!
You are welcome.
Please make a video on Indexes and more specifically Query Performance Fine Tuning Tim
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
@@IAmTimCorey Done. Thanks Tim 😊
Just FYI, I'm a C# developer and at least 25% or more of my time is in SSMS.
Thanks for sharing.
Do you have a course on ms sql or ssms, yours is by far the most helpful sql intro that I have watched!
I do: www.iamtimcorey.com/courses/sql-databases-from-start-to-finish/
Just to say you are awesome.
Greetings from Serbia.
Thank you.
Thank you, this is exactly what I need right now
and it's very useful that you mention how does it look like in corporate environments, I haven't seen that in other tutorials
You are welcome.
I would highly recommend as a free add-on for SSMS, red gate's SQL Search. Very useful
That is a good one.
Also SQL Prompt from Redgate.
Awsome Tim! Thanks :)
You are welcome.
Will you please make a video on How to manage memory management in .NET Core?
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
Do you use Azure Data Studio for any of your dev work? I was wondering because Azure Data Studio is automatically installed alongside SSMS.
I have used it, but I tend to prefer SSMS or SSDT. I considered doing a video on Azure Data Studio as well.
@@IAmTimCorey It looks like ADS with all it's extensions is being setup to replace SSMS/DT.
I use this application daily so it is good that you are covering this important topic.
Thanks!
Hey there, god bless your efforts. i have a simple enquiry as a newbie.
Does a cursor keep track only of the records in the result set or can it return to the original table?
Thanks a lot.
Great Video
Thanks!
Great! Will you do one for azure data studio?
Possibly. We will see how much interest there is in it.
Is attaching a database (via SSMS) to an existing visual studio proj (e.g. .NET Core Web API) a reliable way to have your table data transfer to other environments?
No, you need to use the SSDT project type to take the database schema from one database to be able to use it to transfer to other environments.
Isn’t that localdb thing just a logical endpoint, your actual database was in the appdata folder of the logged in user?
Basically, yes. It is just a folder that you stick database files in.
love ya tim
Thanks.
Can MSSQL be used without Azure? Is MSSQL cloud based?
Sure, you can do MSSQL locally. In development, you can use Microsoft SQL Server Developer Edition for free on your machine (it is not allowed to be used in production). You have the option of running it locally or running SQL in Azure (or other hosts). It is up to you (although Azure is probably the cheapest option).
Sorry guys, but @min 42, why we need to use sanitized data? what des that mean? I understand the point of testing on much bigger DataSet, but I don't understand what is Sanitized data, searching online also says it's a cleaned data from some special chars, so I don't really understand why use sanitized data in this case.
Sanitized data in this context ("a sanitized version of your production database") means that you create a copy of your production database that you can use as a development database. Part of that process is removing or changing sensitive data. For instance, maybe you have a list of email addresses. You wouldn't want that to be the real list, since that would expose those records to people who shouldn't have access to them and since you don't have as strict of protections on your development database. So, you would change each email address to be something else. My personal preference in this specific case is to change any email to the user's first name dot last name at my test domain name. So John.Doe@test.iamtimcorey.com or something like that. To do this safely, though, you might also have already changed the person's last name as well.
Thanks a lot for the explanation, it makes sense, BTW you replying to comments on one year old video is an amazing thing... Have a great day
It's trying to remove the GUI unless you use Azure
I'm not sure what this comment means. SSMS is as close to the GUI for SQL as you typically get.
@@IAmTimCorey I was following a tutorial for setting up api to connect a website and a sql database and the guy had a GUI interface for posting queries and everything to the database but the system just seemed to make the command line available or else seemed encourage going through Azure. I was trying to just follow the instructions explicitly so that I had a problem, then I could compare his Git repository commits to my own. I don't know if I emtered anything wrong, but all of my web searches and my understanding of the documentation pretty much seems like you have to either do command line or else go through Azure.
It's a lot to explain, but I figured out why the application kept closing as soon as I went to open it... it needed to be "repaired" and the repair failed the first time.
The short version is that I couldn't open the program, and from what I had read it looked like Microsoft was doing away with SSMS
How can I sent u a direct private message
I don't offer private consulting, but if you have a question about a course or a purchase, you can email help@iamtimcorey.com.
Have to admit, not watched the video (yet) as I use SSMS v18 daily, the one thing I hate is they removed the run in debug and breakpoints from SSMS. WHY! Have they brought it back for v19, doubt it? Tim, maybe a video about doing SQL stuff and debugging in Visual Studio (unless you have one already).
Edit, NVM -- found you already have one -- ua-cam.com/video/ijDcHGxyqE4/v-deo.html
Glad you found it.
I have a question. you said a business would use a paid version of sql server. I've been in businesses where they were able to use sql server express and it worked fine. Which was great because there was one job where if the express version was not available, then i would have been out of luck because i only got paid 40 to 50 dollars a month and could not afford to pay out of pocket and the business would not be able to afford it either. I would think in most cases, sql server express is the best. i do know if the database size was too large, then they would be forced to pay a lot more for a paid version. the sql server developer version seems useless because of the restrictions.
He also said, the Express edition can be used on production, meaning businesses are allowed to use it without getting the laid version.
I did say Express can be used in production. As for Developer Edition being useless because of the restrictions, that’s absurd. It is just the opposite. Instead of needing to pay a licensing fee to have a version of SQL on your development machine that mirrors what you use in production, you can use a free version. Mirroring production in development is important so that you can experience the same features that your production app has. Don’t complain about what you get for free.
What is Sequel? :) Please say: S Q L
I address this in the video. Both pronunciations are correct. Please stop trying to force one way. The original product was named Sequel (spelled that way). Microsoft people at all levels, including the product owners, say both even in the same video.
@@IAmTimCorey Yeah I've seen the video, Tim
That was exactly the joke about the comment itself hehe
Ah, lol ok.
You should have at least mentioned that "sa" is system admin, "dbo" is database object, it's schema not owner. Maybe you should have mentioned the schema existence at least - access rights can be configured etc.
The second part of the video sounds improvised and boring because it shows almost nothing.
You used to have very informative videos with every unknown detail explained but this one isn't one of them.
I did mention that sa was the system administrator, I did mention that dbo stood for database owner (not object), I did mention that it was a schema, and that there were other options but in small databases, dbo was commonly the only one used. It sounds like you didn’t really watch the video.
@@IAmTimCorey I might have heard some parts wrongly because I was watching on the train to work. I am sorry.