From a san perspective there might not be a reason to split the luns into log, data, etc. However all the Best practice we follow in the physical world should...

I can't speak of Sharepoint 2010 yet, but 2007 can hammer a sql server.

Dividing into files per core isn't recommended. I know that it's a common practice for temdb, but...

After adding 48tb of storage, the size of the database is no longer an issue

Well, the database is a part of our dw/bi (I'm in operations and dba is just one of my chores), but I'm quite sure that some of the data or...

dmoldovan (10/14/2009)

---

You should shrink the db only if you really, really need it - but not on a regular basis. Please take a look at

http://www.karaszi.com/SQLServer/info_dont_shrink.asp

http://technet.microsoft.com/en-us/magazine/2008.08.database.aspx?pr=blog...

anders (8/14/2009)

---

We are in the process of migrating our ssis from 32 bit SQL 2005 to a 64 bit SQL 2008 (amd). We currently having a problem where our ssis...

We just leave the default settings alone for most parts. Including fillfactor. We don't have people dedicated to SQL (they have to cover most of Microsofts product suite like exchange,...

We are looking into using the cloud as an extension of our datacenter, where backup fit in naturally. The challenge is to find the tools to do and manage it...

While SQL is a great DBMS it's not on par with oracle and that level yet (as the price reflects). Also some of the scalability problems caused by the locking...

Well it depends on your business, if you're a Microsoft house I would recommend hyper-v if you have a mixed environment I would take a closer look at vmware or...

Jeffrey Williams (6/17/2009)

---

I would recommend not using a single file device and continue using multiple files. The problem you are going to run into is very simple. Part...

I'm using equallogic, our choice was based on easy maintenance (we only spent time when doing new luns or modifying luns). It has both a great management interface and performance...

It's far easier upgrading the SQL Server, than upgrading from Ax 3.0 til Ax 2009 with a highly customized application. I'm sure that Ax2009 have major performance improvements, but their...

I'm in the exactly the same situation, got a Axapta 3.0 on a SQL 2000 and want to move it to a SQL 2008. I'm going to set up a...