October 22, 2010 at 10:57 am
Our developers were developing on SQL Server 2000; two weeks ago our main production environment and its corresponding Test and development servers were changed to SQL Server 2008.
What are the top ten things a developer should know about SQL Server 2008?
October 22, 2010 at 11:19 am
That it's still SQL
All the things they should know about any ACID, relational database
Set-based CRUD
SQL is Declarative, not procedural/OOP
Table input parameters
Merge
Modifications to "Values" (data sets)
That's not 10, but it'll get you started.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
October 22, 2010 at 11:34 am
Here are a few:
- database mail (as opposed to SQL MAIL)
- SQL CLR (for file-system operations, web services, regular expressions)
- service broker
- "EXEC @sql AT LinkedServerName" syntax
- module signing (EXECUTE AS clause)
- Database Tuning Advisor
- SQL Server Profiler
- Dynamic Management Views for Index Stats, Missing and Unused Indexes, cached exec plans etc
- Working with SQL Server Management Studio
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
October 22, 2010 at 11:46 am
- Remove all the hints and tweaks you use with sql2000 !
- check out the graphical execution plan and see how it proposes for new indexes. Keep in mind you'll still have to test if that index would actually serve you well, but at least it give a starting point
- try out sql 2008s new tsql stuff - and the ones added with sql2005 - because they may serve better than the SQL2000 equivalents.
- Lean to use Books online ( SSMS query pane shift+F1 )
- don't use the create view wizard ! The generated queries are still horrible.
- Thinking sets pays of way better than it used to in SQL2000.
- Check your deadlock monitoring results (startup parameters at instance level '-T1222' )
- know about the DMVs. Especially the ones that show missing indexes and actual cached query plans. In many cases developers will not have the auth. to see these on production boxes, but the least they can to is ask for a regular export e.g. during startup periods of a project in production
- If they used sql mail, make them switch to dbmail asap !
- don't just start doing CLR stuff, but provide guidance rules.
- don't use any non-standard-activated option, unless you have no other choice. e.g. xp_cmdshell, ...
- replace all your sp_oa... code with the more stable equivalent if you need to.
- many dmvs will need extra authority to see more than your own connections related stuff.
I hope you've taken the opportunity to optimize instance and installation level security, configuration, ....
- Go for 64-bit db solutions if you can.
just to name a few starting points 😎
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply