Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Microsoft Business Intelligence Project Booster Kit


Microsoft Business Intelligence Project Booster Kit

Author
Message
Oleg Netchaev
Oleg Netchaev
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1693 Visits: 1808
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
Siddharth Mehta
Siddharth Mehta
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
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.
Sam Greene
Sam Greene
SSC Veteran
SSC Veteran (253 reputation)SSC Veteran (253 reputation)SSC Veteran (253 reputation)SSC Veteran (253 reputation)SSC Veteran (253 reputation)SSC Veteran (253 reputation)SSC Veteran (253 reputation)SSC Veteran (253 reputation)

Group: General Forum Members
Points: 253 Visits: 584
The title RSS Scripter.

Should be chagned to RSScripter.

Enjoying the concept so far...
Siddharth Mehta
Siddharth Mehta
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
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.
tony-591909
tony-591909
Forum Newbie
Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)

Group: General Forum Members
Points: 8 Visits: 455
Thanks Siddharth. You're a brilliant young man. Keep them coming. All the best. Tony
charlie.smith
charlie.smith
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
Points: 7 Visits: 54
Good work Siddharth. Thank you for sharing this with us.
melina386
melina386
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 6
excellent article about the Microsoft Business Intelligence Project Booster Kit
thanx for posting for us
Data entry india
melina386
melina386
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 6
excellent article about the Microsoft Business Intelligence Project Booster Kit
thanx for posting for us
Data entry india
jacob sebastian
jacob sebastian
SSC-Addicted
SSC-Addicted (472 reputation)SSC-Addicted (472 reputation)SSC-Addicted (472 reputation)SSC-Addicted (472 reputation)SSC-Addicted (472 reputation)SSC-Addicted (472 reputation)SSC-Addicted (472 reputation)SSC-Addicted (472 reputation)

Group: General Forum Members
Points: 472 Visits: 2523
Thanks Siddarth!
It is a very interesting article.

.
Jamie Thomson
Jamie Thomson
SSC Eights!
SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)SSC Eights! (885 reputation)

Group: General Forum Members
Points: 885 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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search