Whitepaper for developers
-
Does anyone know of a good whitepaper that gives the changes in best practices for developers? I'm looking for something that specifically targets the changes that the developers are going to see not the changes for the DBAs.
Any suggestions anyone?
kenneth Fisher
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
-
Heh... I have to laugh at what they call "best practices" for most performance issues... no where do they say "review all code for possible performance issues before it goes into the database" nor do they ever say "when you've identified a proc that is causing performance issues, you may have to rewrite it because it's obviously crap code"
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Ah, but if you did that, wouldn't that be crossing the production / development line and violating SOX?
-
Maybe... but how ya gonna know about SOX violations if no one reviews the code? 😛
Bottom line is to protect the data and the server. Slow running code has the potential for doing neither and it needs to be fixed. 😉
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Unfortunatly it doesn't look like they have what I need. I'm looking for something I can give my developers that will tell them whats new for them in 2005. We arn't using full text, xml, analysis services etc. Just basic SQL. These are .net and web developers using SQL as a back end. Any other suggestions?
Thanks
Ken
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
-
Heh... you mean other than hiring someone who actually "knows" SQL? (Just having a bit of fun, Kenneth 😉 )
There are a couple of dozen articles on this forum about the differences (enhancements) between SQL Server 2k and 2k5... Steve Jones wrote a good number of them... trying doing a search on this site... most of them are pretty good "summaries".
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
send them on a sql training course; I'm constantly surprised that many companies do not feel a need to train their dot net developers in T-SQL / SQL Server - of course their code and apps are crap, as Jeff pointed out; but hey we can always blame SQL Server or the DBA's.
I did a presentation on best practices - send me a private meaage and I'll zip and mail it ( it's a powerpoint )
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/ -
ps. I could recommend Andrex < grin >
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/ -
As a developer, I agree with sending them to SQL Server training! I fought to get some brought in-house, since I came from a COBOL / MS-Access background. The un-educated will try to relate what they know to these new software platforms, and that doesn't always work (been there, got bit, got training!)
Here there be dragons...,Steph Brown
-
Unfortunatly there are 2 very good reasons why our developers will never be sent to a sql server training class.
1) Several hundred developers
2) A VERY VERY cheep company
Not a good combination 🙂
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
-
Several hundred developers? What you really need is a good set of development standards... 😉
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Don't get me wrong. The SQL code these guys are doing is fairly good. I'm not worried about it in that sense. I'm just looking for something I can give them that shows what they can't do any more in 2005 and what new features they could now take advantage of.
Kenneth Fisher
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
-
Like I said... there's a couple of summary articles on SQLServerCentral.com... just do a search for them... some thing like "Differences between SQL Server 2000 and 2005" should do...
Of course, you could also look in Books Online for what's changed... it also has a summary.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply