![]() Otherwise, give it a try and let me know if it works. If you have other ideas, I’m sure Redgate would appreciate suggestions. What is the outline and structure of my code. I’m not sure how useful this feature is, but it’s now in my mind to try a few times and see what I think. In a long set of code, this might help me make sure I’ve actually included the CATCH, among other things. However, in AdventureWorks, there is a procedure that shows me a TRY CATCH. I can’t see the base tables here, which isn’t useful. ![]() What about other types of code? I looked at a CTE, which wasn’t that helpful. This let’s me see that the code is more of a procedural construct, which looks like this: The actual code is a bunch of math changes, and I could have used SET, which might have helped here. Not a lot of information from the SELECTs, but I do see some looping. In this case, I see something more complex. In this one, there is some looping, as it’s a looping type of problem (to me). I picked a longer script from some of the Advent of Code stuff I’ve been slowly working on. Depending on length, this might be helpful to remind me or let me see if I’ve dropped all the code I expected. However, I could also see that easily if I looked at the script. I can see I cleaned up the CREATE with the DROP. ![]() I got what I expected, an ordering of various operations. I had a demo script for a customer, and I ran it there. I had guessed that it might look at the code and give me some outline, which is what it does, but I wasn’t sure how it might work. I have never used this feature, but someone was asking for feedback on Prompt, and I noticed this in the menu: Summarize script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |