Some of the int fields are loaded as YYYYMMDD so these may be good partitioning columns also but I see what you say about the indexes (looking at the dmv's...

CREATE TABLE [dbo].[dim_dr](

[dr_sk] [bigint] IDENTITY(1,1) NOT NULL,

[dr_nk] [varchar](30) NOT NULL,

[s_sk] [bigint] NULL,

[s_nk] [varchar](30) NULL,

[dr_frdate_hq_sk] [int] NULL,

[dr_frtime_hq_sk] [int] NULL,

[dr_tdate_hq_sk] [int] NULL,

[dr_ttime_hq_sk] [int] NULL,

[dr_frdate_local_sk] [int] NULL,

[dr_frtime_local_sk] [int] NULL,

[dr_tdate_local_sk] [int] NULL,

[dr_ttime_local_sk] [int] NULL,

[dr_frdate_utc_sk]...

That was my understanding but this is a dimension. The large fact tables are all partitioned, they are a similar size to this one.

This is most likely down to permissions.

Check your root folders on file structure.

From a bit of testing it appears you cannot connect to SQL 2008 R2 using the SQL Server ODBC driver (SQLSRV32.DLL) without specifying the port number.

I can connect successfully using...

Thanks for the response,

I changed from CNAME to A record and I have the same issue in that I have to specify the port number.

If I remove aliasing from the...