Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » Article Discussions » Article Discussions by Author » Discuss Content Posted by Nanda Kishore » SQL Server 2005 Best Practices
Add to briefcase
25 posts, Page 1 of 3
123»»»

SQL Server 2005 Best Practices Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
NandaKishore
Posted Thursday, December 01, 2005 11:47 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, October 06, 2006 6:58 AM
Points: 2, Visits: 1
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/nKishore/sqlserver2005bestpractices.asp
Post #241268
Chris Hedgate
Posted Wednesday, January 04, 2006 4:38 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Saturday, February 28, 2009 6:51 AM
Points: 1,489, Visits: 7
What do you mean by "Avoid code that assumes all metadata is publicly visible"? As of SQL Server 2005 Microsoft is now recommending usage of the (documented) catalog views and dynamic management views for accessing metadata.

And regarding the list of documented columns that return NULL or 0, well all of those columns are part of catalog views that exist only for backwards compatibility with the old system tables. For instance, instead of using sysindexes (which is actually called sys.sysindexes to be exact) you should use sys.indexes.



--
Chris Hedgate http://www.hedgate.net/
Contributor to the Best of SQL Server Central volumes
Articles: http://www.sqlservercentral.com/columnists/chedgate/
Post #248032
Grant Fritchey
Posted Wednesday, January 04, 2006 6:04 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 3:57 PM
Points: 13,371, Visits: 25,152

Well written article, but a couple of points.

It doesn't really get into Best Practices much at all. With the exception of some SQL 2000 best practices that will prevent an upgrade, there's almost nothing here in terms of the list of "do this", "don't do that" and "this would be a good guideline to follow."

Also, you talk about database mirroring, yet, according to the documentation provided, this is not currently supported by MS so this can hardly be considered a "Best Practice."

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #248056
TDuffy
Posted Wednesday, January 04, 2006 6:54 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, September 15, 2008 12:02 PM
Points: 1,318, Visits: 57

How can you state "Usage of DBCC commands is not supported in SQL Server 2005"? This is just not true.

Some DBCC commands are deprecated (e.g. DBCC PINTABLE), but such a blanket statement is false.

Terry


Post #248069
PBirch
Posted Wednesday, January 04, 2006 7:46 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, December 24, 2008 11:15 AM
Points: 575, Visits: 35
I agree. I have been using DBCC commands in 2005 for months with few issues. That is an odd phrase.

This article, will ok, was not a best practices. It was more of a "new stuff" article.

The author did not mention that the semicolon is a statement terminator used in t-sql. Using 7 and 2000 you could write sql statements for pages and never use a semicolon. In 2005, using the semicolon is still not mandatory; it is ANSI-compliant.

You will notice that the code from Microsoft uses it and there are a few gotchas. For example, if you use the CTE(which was not mentioned in the article) in a batch of statements, the statement before the CTE definition must have a semicolon.

Quand on parle du loup, on en voit la queue
Post #248098
Ian Yates
Posted Wednesday, January 04, 2006 8:13 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Sunday, September 16, 2012 3:26 AM
Points: 1,038, Visits: 443

And where is the whitepaper?
"Please refer to this white paper for a better understanding of partitions in SQL server 2005."

Sounds like some cut + paste?


Post #248118
DCPeterson
Posted Wednesday, January 04, 2006 10:10 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 7:50 AM
Points: 1,032, Visits: 389
I think what Nanda meant was that the meta data is now secured along with access to the objects themselves, so you can't assume that any given user has access to any particular piece of meta data.  At least that's how I read it.


/*****************

If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek



*****************/
Post #248159
Chris Hedgate
Posted Wednesday, January 04, 2006 10:20 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Saturday, February 28, 2009 6:51 AM
Points: 1,489, Visits: 7
Yes, that might be what was meant. Not very clear though..



--
Chris Hedgate http://www.hedgate.net/
Contributor to the Best of SQL Server Central volumes
Articles: http://www.sqlservercentral.com/columnists/chedgate/
Post #248169
stevehindmarsh
Posted Wednesday, January 04, 2006 3:59 PM
SSC Eights!

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

Group: General Forum Members
Last Login: Wednesday, May 08, 2013 12:50 AM
Points: 852, Visits: 519

Hmmm - not really a best practices list - more a new features description. 

Would a best practice be 'turn off CLR enabled' sp_configure option until ordered to turn on by senior management '


Post #248261
Chris Hedgate
Posted Thursday, January 05, 2006 2:28 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Saturday, February 28, 2009 6:51 AM
Points: 1,489, Visits: 7
Well, first of all you do not need to, CLR is disabled by default. But enabling it does not really do a lot unless anyone starts to use it. Being told by senior management to enable it would make me very disheartened, since that is not something they should concern themselves with. But I do think that there are many compelling cases for enabling and using it, even though I am in general quite reluctant of it.



--
Chris Hedgate http://www.hedgate.net/
Contributor to the Best of SQL Server Central volumes
Articles: http://www.sqlservercentral.com/columnists/chedgate/
Post #248351
« Prev Topic | Next Topic »

Add to briefcase
25 posts, Page 1 of 3
123»»»

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.