I saw this out on the SQL Authority blog and thought that I'd pass the link around, seeing as the author doesn't want it printed or even downloaded. It's certainly not a bad thing to have a SQL reference, or change it up, even your style is already ingrained into your brain. Check out this link below for a decent SQL notation reference. I find that I already follow alot of these standards, except for the lookup table notation. I always used "LKP_Tablename" notation when creating those. I think I'm going to change my style.
Let me know what yinz think.
http://www.pinaldave.com/sql-download/SQLServerGuideLines.pdf
Friday, July 30, 2010
Friday, July 23, 2010
list all tables in a database
So I'm documenting a database with 21 tables in it. I wanted A quick way to get them listed. Voila:
SELECT *
FROM information_schema.Tables where table_type = 'base table'
note that I added the WHERE clause. Without it, I also got all of the views.
SELECT *
FROM information_schema.Tables where table_type = 'base table'
note that I added the WHERE clause. Without it, I also got all of the views.
Friday, July 2, 2010
time tracking tool
I was reading about Toggl, which seems pretty cool, and free.
http://www.toggl.com/public/tour
Don't know how people are tracking their time these days. I liked Allnetic's tracker until they decided to charge for it :P
Since toggl is web based you don't need to be tied to a machine to track your time, although I don't know if the desktop tool syncs up - I would assume so though.
http://www.toggl.com/public/tour
Don't know how people are tracking their time these days. I liked Allnetic's tracker until they decided to charge for it :P
Since toggl is web based you don't need to be tied to a machine to track your time, although I don't know if the desktop tool syncs up - I would assume so though.
Subscribe to:
Posts (Atom)