Controversial: SQL
-
not sure if this is even relevant or helpful: Transact-SQL Code Snippets - SQL Server Management Studio (SSMS) | Microsoft Docs[^] I save my sql to an organized sql folder locally, of which you could add to source control or cloud storage if you wanted to. it's not the greatest method, but I have been doing it this way for years and will probably not change. :-D
-
Visual has/had a code snippets kind of thing. Maybe that could be adapted.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
You can also set it up in the VS toolbox as boilerplate code to drag and drop into an app - I use it for boilerplate SQL access to be "tuned" for a specific purpose.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
There's no great way to : 1) store and categorize good sql 2) also would like a way to insert table names and field names so you could select some things and then just fire off the SQL. 3) need a place for notes about what the sql actually does. I tend to forget sql very fast -- sql is boring and declarative and I always have to look at it too much to remember what it does. Sometimes I just want to find an old query that does that thing you know? :)
We have a database for saving queries like that as stored procs. Everybody has their own schema, and can see each other's procs. Most of them are specific to the table/view being queried.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
My current project has a folder in google drive (coworkers choice, I'd've added a folder in our git repo) to store all the supposedly 1 off queries (if they said they wanted it repeatedly we'd have a report/import page) we've ran for the customer so they're available for the next time they ask.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
Yeah, I did something similar by creating a document on Google Drive. Just wish there was a better way to manage them with comments etc. By "better way", I mean i could just think of a query I've done in the past and it would appear on my screen. :laugh:
-
MSSQL snippets works perfectly for me except you need to rabbit through the category folders to find the exact one you need :-O. Tis a bitch when you can't remember the category/folder it lives in.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
- I simply use the file system. Every file gets a [declarative name].sql, so you can doubleclick and it will start SSMS or whatever program is associated. The master folder is also added to TortoiseHg for versioning 2) Then you need to use dynamic SQL, which is a whole can of worms by itself, and also a possible source of so called SQL-injection 3) I use a fancy invention called Comments for that. Just add them to forementioned Files In Oracle you can also add comments directly to the tables and columns themselves, but in SQL Server you only have Extended Properties, which aren't nearly the same thing
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
Jörgen Andersson wrote:
- Then you need to use dynamic SQL, which is a whole can of worms by itself, and also a possible source of so called SQL-injection
I'm just talking about a local resource that I would use to call up previous queries that I've had to do to examine or update data manually. All of our work is done view SPs -- there are no ad-hoc SQL that are allowed to run against our DBs.
-
There is no good way to store good SQL queries for future use. Just, no good way. :rolleyes:
Quote:
There is no good way to store good SQL queries for future use.
What's wrong with stored procedures?
-
There is no good way to store good SQL queries for future use. Just, no good way. :rolleyes:
How about [Solution Explorer - SQL Server Management Studio (SSMS) | Microsoft Docs](https://docs.microsoft.com/en-us/sql/ssms/solution/solution-explorer?view=sql-server-ver15) ?
Check out my blog at http://msdev.pro/
-
There's no great way to : 1) store and categorize good sql 2) also would like a way to insert table names and field names so you could select some things and then just fire off the SQL. 3) need a place for notes about what the sql actually does. I tend to forget sql very fast -- sql is boring and declarative and I always have to look at it too much to remember what it does. Sometimes I just want to find an old query that does that thing you know? :)
Sounds like templates: Template Explorer - SQL Server Management Studio (SSMS) | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Well, I have something like that too, but it's difficult to find the right one amidst all of the other chaff. I wish there was a way to categorize them or something like that. And don't offer me the idea of making sections in my text file, cuz i'm lazy (of course -- I'm a dev). :-D
-
There is no good way to store good SQL queries for future use. Just, no good way. :rolleyes:
SQL is too broad term. IBExpert[^] for Firebird has it and much more[^] .
-
There is no good way to store good SQL queries for future use. Just, no good way. :rolleyes:
A lot of tools come to mind on this topic. Notepad, or Notepad++: I recommend using "AGENT RANSACK" a very fast multi-threaded Search engine. (You can start the search in your ROOT file for the SQL files) (Side note: This is my number one favorite tool) Organize the SQL files, by INDEXING Them (aka: "Tags") INDEX: (Example) #DATE Ex: 01/01/2021 #PROJECT Ex: (NAME) #TYPE Ex: (SELECT INSERT UPDATE DELETE) #NOTATION Ex: That query for the thing I had to do at 1AM ...more as needed ---------------------------------------------------------------- Open "Agent ransack" and search on terms in the sql. This could be all put in a database, but I think that may be a bit too much. You want something simple, and you want to find it fast. You already have a body of SQL that is not indexed. Start indexing all NEW SQL FILES, and as you revisit the old ones, (that are not indexed), Index them as you go along. Keep it all in one file, or multiple files, doesnt matter much with Agent Ransack. So what you wind up with is your very own Google Search for your sql. Keep It Simple, keep it moving.
-
I keep a text file of 'em: "GoodSQLQueries.txt" it's called. It's easy to copy'n'paste 'em when I need 'em. Or just use an SP. What's the problem?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
I use OneNote -- I have a notebook for each database, with sections labeled by tables and/or area. Each query or code segment has a comment briefing describing what it does. This makes hunting for things much easier.
-
There is no good way to store good SQL queries for future use. Just, no good way. :rolleyes:
I would suggest a couple of things: - a stored procedure that is just a collection of these wonderful SQL statements that is commented well and set up to NOT be runnable (comment out the whole thing between /* and */, probably) - set up a comment area above each piece of code with keywords or details about what the code does and what it would be useful for - using a search (CTRL-F) on the stored procedure you called GreatCodeToMaybeReuseSomeday (or whatever) to find the SQL of interest. - Copy and paste the code you found. Probably the closest to "think it and it will appear"
-
There is no good way to store good SQL queries for future use. Just, no good way. :rolleyes:
Just a thought: Use a library like JsonQL to convert SQL to a JSON representation and store them in MongoDB with descriptive metadata. Search on the content and/or metadata.
-
Quote:
There is no good way to store good SQL queries for future use.
What's wrong with stored procedures?
Member 13301679 wrote:
What's wrong with stored procedures?
I mean like a development studio type of thing where you can select a particular SQL statement that you want to run manually when you're examining data and designing queries. We use SPs for all interactions with DB but I'm talking more about a code reuse type of thing. I guess I could create a library of SPs and then run those when I need to, but I'd still need a way to manage them with names and stuff so I could remember what they do. I guess it is really because I'm in the midst of designing queries for a large system and I only have to do this every 2 or 3 years so I have a long time away from it.
-
How about [Solution Explorer - SQL Server Management Studio (SSMS) | Microsoft Docs](https://docs.microsoft.com/en-us/sql/ssms/solution/solution-explorer?view=sql-server-ver15) ?
Check out my blog at http://msdev.pro/
-
Member 13301679 wrote:
What's wrong with stored procedures?
I mean like a development studio type of thing where you can select a particular SQL statement that you want to run manually when you're examining data and designing queries. We use SPs for all interactions with DB but I'm talking more about a code reuse type of thing. I guess I could create a library of SPs and then run those when I need to, but I'd still need a way to manage them with names and stuff so I could remember what they do. I guess it is really because I'm in the midst of designing queries for a large system and I only have to do this every 2 or 3 years so I have a long time away from it.
Quote:
I mean like a development studio type of thing where you can select a particular SQL statement that you want to run manually when you're examining data and designing queries.
MySQL Workbench allows that, including loading and saving the files just like an IDE, keeping files in different tabs, etc.
-
Sounds like templates: Template Explorer - SQL Server Management Studio (SSMS) | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
That does look good but...
Link provided said
Important This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
I didn't know that, thanks for the info. I have another one: [Download and install Azure Data Studio - Azure Data Studio | Microsoft Docs](https://docs.microsoft.com/en-us/sql/azure-data-studio/download-azure-data-studio?view=sql-server-ver15) Maybe this does what you want? I think it also works with SQL Servers that are not in Azure but I didn't test that.
Check out my blog at http://msdev.pro/
