• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Dynamo_Maestro

SQL Server Table naming conventions

4 posts in this topic

When you create a new table in SQL Server the default name is dbo.Table_# with # being the new table value. I rename my tables without the dbo. and it is almost always plural.  Looking at TFS collections I noticed all the tables were named with one of the following prefixes Codesense.tbl_ / dbo. / dbo.tbl_ where they were mostly singular names regardless of the prefix.

 

There is a fair amount of noise online on whether tables should be plural / singular online but nothing really mentioned prefixes such as dbo. or dbo.tbl_.

 

My question isn't really about naming tables with plural / singular names but more about the dbo. dbo.tbl_ prefix. Is this the SQL version of Hungarian notation where I can freely avoid or is there some kind of rule where it is best to follow this practice and name tables with dbo. / dbo.tbl_ prefixes?

 

Edit: This applies to other areas of the DB too, almost everything is created with dbo. but I figured I would figured I would talk about the table prefixes only

Edited by Strix_Overflow
0

Share this post


Link to post
Share on other sites
The dbo part is the schema name. It's sort of a namespace that you can connect database logins to. It doesn't have to be "dbo", you can create any schemas you want and set tables and other objects as owned by that schema.

I never saw the schema name as part of the table name, not sure if other people see it that way though.
0

Share this post


Link to post
Share on other sites

Thanks for the reply. I had a look at this http://technet.microsoft.com/en-us/library/dd283095(v=SQL.100).aspx after I wrote the question. I was quite surprised I never came across this but then after doing some reading it makes sense as I am not doing DB work in a team however due to the way it helps combining tables I must admit it is much better than my current 'separate by underscore' approach.

 

Anyway thanks for the reply.

0

Share this post


Link to post
Share on other sites

Personally I name tables after what they contain, so Weapon, Player, Monster, etc.

 

I could maybe see the use in using tbl_ to differentiate between tables, views, etc, but in practice I've never needed it.

0

Share this post


Link to post
Share on other sites

dbo.tbl_ prefix

 

The use of prefixes such as tbl, sproc, vw (view), func (function), clr and so on are really just hints as to what the type of the database object you are dealing with is.

 

Sometimes when writing queries it is handy to know that the table you are querying really is a table and not a view. Mostly helpful in really big projects (i.e. "I know I have to call a stored procedure, but what was the name again?? oh i'll type .sproc_ first to get the list of 100 in code completion and hide the 100's of tables").

 

Personally I don't care what naming conventions are used as long as they are consistently applied, my old boss on the other hand would often say "Mr Codd would be turning in his grave!" when he saw something he didn't like - including tbl_ prefixes and pluralisation smile.png.

 

(edit: sometimes what technology you use impacts your naming convention, e.g. using the Entity Framework or other ORM tools might steer you towards using singular or plural depending on the implementation and what the code it generates looks like)

Edited by spazzarama
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0