Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

Microsoft Business Intelligence Project Booster Kit Expand / Collapse
Author
Message
Posted Tuesday, November 24, 2009 12:12 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 8:33 AM
Points: 1,676, Visits: 1,760
Siddharth,

This is a very useful article, thank you. I do have some comments regarding the Standards for T-SQL Coding document. There is no doubt that existence of such document is fully justified for a successful implementation of any project, but I believe that you should consider adding a small disclaimer after the link to your "sample of one such document" stating that this is just a sample which by no means is intended for anybody’s serious consideration. This is because the sample document is ridden with quite few questionable and even plain wrong recommendations. Your article is read by SQL Server Central subscribers of all levels, and a small disclaimer could be useful. Here is the small list of examples which I believe maybe considered as questionable by many:

"System level stored procedures are named using a prefix 'SP__' (two underscores)".

This is still ill advised despite the two underscores IMHO.


The comment about the text data types:

"There are a lot of bugs associated with replicating tables containing text columns. So, if you don't have to store more than 8KB of text, use CHAR(8000) or VARCHAR(8000) datatypes instead."

This is just plain wrong because the page size in SQL Server is 8K, the maximum number of bytes of in row data of a single record is 8060, and while SQL Server engine will allow you (with warning) to create a table which can potentially have records wider than (if you opt for varchar(8000)), maintaining a table like this is a recipe for disaster because this table will be subjected to occasionally (not always) failing to insert and/or update some of its records.


"IDENTITY columns can run out of numbers at some point, depending on the data type selected; numbers can't be reused automatically, after deleting rows; and problems may arise if you are using replication. So, come up with an algorithm to generate a primary key in the front-end or from within the inserting stored procedure".

Even Oracle developers don’t use this approach any more as they have nextval function to their disposal to retrieve the next available value from existing sequence. With SQL Server there are many different ways to deal with issues such as filling the holes after deletes (if one perceives this as an issue) and setting up seeds for replication to still work flawlessly.


"Minimize the use of NULLs, as they often confuse the front-end applications, unless the applications are coded intelligently to eliminate NULLs or convert the NULLs into some other form."

If developers are not capable to intelligently code the applications then it is too bad for them, but still DBA should not just nod and start creating a whole bunch of defaults to insert empty strings, zeroes and 9999-12-31s in place of respectable null values.


Lack of a small disclaimer aside, the article is great. I really like the Microsoft Business Intelligence Project Booster Kit section.

Oleg
Post #824072
Posted Tuesday, November 24, 2009 12:21 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, March 13, 2011 4:45 AM
Points: 18, Visits: 94
Thanks for drawing my attention towards this thing. I do agree with your advise.

I mentioned it's a sample document ("sample of one such document"), and sections of it would have gone obsolete or may be a wrong suggestion.

My intention was to suggest a template or prototype of sections to be covered for creating such document. Next time I would take care of this point. Thanks for the feedback.
Post #824075
Posted Tuesday, November 24, 2009 1:27 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, September 25, 2014 7:11 AM
Points: 253, Visits: 546
The title RSS Scripter.

Should be chagned to RSScripter.

Enjoying the concept so far...
Post #824118
Posted Tuesday, November 24, 2009 1:49 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, March 13, 2011 4:45 AM
Points: 18, Visits: 94
There are 3 typos in this article

1) I have mentioned "She" for Jamie Thomson, instead of "He".
2) In the complexity measure section, it should be "allocating" instead of "allocation"
3) Instead of RSS Scripter, it should be RSScripter. I should have mentioned author Jasper Smith's name besides it.

I am already aware of it. Still, thanks for pointing this out and thanks for your feedback.
Post #824132
Posted Tuesday, November 24, 2009 6:49 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, February 2, 2014 9:35 PM
Points: 8, Visits: 452
Thanks Siddharth. You're a brilliant young man. Keep them coming. All the best. Tony
Post #824245
Posted Wednesday, November 25, 2009 6:34 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, May 6, 2011 6:31 AM
Points: 7, Visits: 54
Good work Siddharth. Thank you for sharing this with us.
Post #824480
Posted Wednesday, November 25, 2009 9:17 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, February 3, 2010 8:00 PM
Points: 5, Visits: 6
excellent article about the Microsoft Business Intelligence Project Booster Kit
thanx for posting for us
Data entry india
Post #824708
Posted Wednesday, November 25, 2009 9:39 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, February 3, 2010 8:00 PM
Points: 5, Visits: 6
excellent article about the Microsoft Business Intelligence Project Booster Kit
thanx for posting for us
Data entry india
Post #824736
Posted Thursday, November 26, 2009 12:07 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, December 24, 2013 4:42 AM
Points: 460, Visits: 2,523
Thanks Siddarth!
It is a very interesting article.


.
Post #825069
Posted Friday, November 27, 2009 2:30 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, November 10, 2013 11:52 AM
Points: 877, Visits: 188
SBS-291204 (11/24/2009)
Mate, I think you'll find Jamie Thomson is a man... unless he's not telling us something?


Thank you man!
I didn't know about this article until yesterday evening when Siddharth blurted out in front of about 40 fellow SQL folks that he thought I was a woman! Also, the law of sod means that I had taken a couple of my project colleagues along with me for the 1st time - so you can imagine the stick that I'm getting at work this morning!!!

I am, and always have been, a bloke!


Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
Post #825493
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse