64 bit windows (RSS)

64 bit windows

Yukon and the 64 bit story

Besides my personal interest in SQL Server 2005 , at work I am asked to plan ahead for deployment of Yukon. As the company itself is in the midst of a technology transition, including an investment and future proof database platform, I am was considering 64 bit Yukon. 

But from MS the 64 bit story is not very good in regards to Yukon (and Itanium in particlar). And I am a bit worried. With all the BI goodness in Yukon, without a good 64 bit story, how can one take THE right decision?   

I know that 64 bitness will be included in beta 3, but is it not a bit late?

 

some links:

http://www.microsoft.com/sql/64bit/default.asp
http://www.informit.com/articles/article.asp?p=170820
http://www.ftponline.com/vsm/2004_en/magazine/features/rjennings/
http://weblogs.asp.net/tims/archive/2004/06/28/167675.aspx
http://www.microsoft.com/seminar/events/series/msdn64bitwin.mspx
http://www.lemanix.com/nick/archive/2004/09/11/1261.aspx
http://blogs.sqlxml.org/vinodkumar/archive/2004/01/16/328.aspx
http://www.thespoke.net/MyBlog/Hirantha/MyBlog.aspx
http://www.bsdg.org/2004/09/get-ready-for-net-20-with-danny-thorpe.shtml

SQL Server scalability (64 bit)

SQL Server scalability casestudies for IT managers:

http://www.microsoft.com/sql/64bit/productinfo/casestudies.asp

other
http://www.enertia-software.com/item.asp?item=622
http://www.intel.com/business/casestudies/raymond_james.pdf
http://www.intel.com/business/bss/products/server/itanium2/testimonials.htm
http://www.intel.com/business/casestudies/koehler.pdf
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=0
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=1
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=2
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=3
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=6
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=8
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=9
http://www.intel.com/business/bss/swapps/server2003/testimonials.htm?showAll=true&selected=11

http://www.unisys.com/products/es7000__servers/news_a_events/all__news/01218375.htm

http://www.hp.com/products1/itanium/testimonials/banca.html
http://www.hp.com/products1/itanium/testimonials/comp_usa.html
http://www.hp.com/products1/itanium/testimonials/finnish.html
http://www.hp.com/products1/itanium/testimonials/denizbank.html

some posts:

http://blogs.msdn.com/brada/archive/2004/03/10/87635.aspx
http://weblogs.asp.net/rwlodarc/archive/2003/04/24/6006.aspx
http://stupidevilbastard.com/archives/2004/02/18/intel_admits_64_bit_is_next_big_thing.php
http://weblogs.asp.net/jdennany/posts/31691.aspx
http://weblogs.asp.net/volkerw/archive/2004/02/25/80175.aspx
http://weblogs.asp.net/oldnewthing/archive/2003/11/19/55757.aspx
http://weblogs.asp.net/frankarr/archive/2004/03/25/95564.aspx
http://weblogs.asp.net/mdavey/archive/2004/03/19/92568.aspx
http://weblogs.asp.net/wallym/archive/2004/01/29/64749.aspx
http://weblogs.asp.net/pleloup/archive/2003/10/29/34389.aspx
http://weblogs.asp.net/volkerw/archive/2004/04/12/111860.aspx
http://sqljunkies.com/WebLog/jt_kane/archive/2003/09/29/247.aspx

 

 

 

 

Database scalability - How scalable is MS SQL Server ?

Today I got news: a joint venture of my employer will merge it's IT operations into ours. What does it mean to me?My largest DB table goes from 100 million to 500 million rows. What can I make to improve MS SQL Server database scalability?

Good things for database scalability:

  • do the right indexes(avoiding autocounters if possible)
  • partition tables' data
  • put old data ointo separate table (archive)
  • distribute DB, Temps DB and Transaction logs to different filegroups 
  • distribute above to hard drive partitions
  • use nolock, readpast and/or READUNCOMMITTED where possible
  • shift processing of some data to out of business hours times

To avoid:

  • triggers
  • cursors
  • PK-FK relations (CHECK constraints are cheaper)

for SQL Server 64 bit database scalability check out:

http://dotnetjunkies.com/WebLog/stefandemetz/archive/2004/01/21/5853.aspx
http://dotnetjunkies.com/WebLog/stefandemetz/archive/2004/05/16/13724.aspx