[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

SQL Server Migration

Posted on 2014-03-07
4
Medium Priority
?
247 Views
Last Modified: 2014-03-15
Hi All

Any ideas here. I am doing a server migration as the organisation that I am contracted to has changed the service provider of their infrastructure and the two servers that I run my services through are on the old domain.

As such I have set up a 'stepping stone' virtual server on the new domain to provide un interrupted service whilst I move my two servers over to the new domain.

On this stepping stone server the only difference is that my two physical servers have enterprise SQL 2008R2 (database server) and standard SQL 2008R2 (cube database and web server), whereas the stepping stone server that has both the databases and cube databases and web service is running standard SQL 2008R2.
The only reason for having enterprise on the data server is for memory allocation. I have not used any of the additional enterprise features (so indexed views etc).

However one of the measures on my cube database gives me a -1 #IND error but only for one of the fiscal years. This fiscal year of data is the latest and is added in a union as it is temporarily coming from a different source and so I dumped it into different staging, release tables and unioned the data into the cube fact table in the data source view. The reason for this is that it has a different structure but is only a temporary source. The original source of data is expected to return shortly and will replace the temporary source period, so I will be removing the union statement from the data source view.

This all works perfectly on the original set up. I cant understand why its giving me this error on the new server.

Any ideas would be greatly appreciated.

Same service packs and everything.
0
Comment
Question by:trawley
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 3

Author Comment

by:trawley
ID: 39913002
Think I might have found the problem.
0
 
LVL 9

Expert Comment

by:Vijaya Reddy Pinnapa Reddy
ID: 39913052
Please mark your question as answered
0
 
LVL 3

Accepted Solution

by:
trawley earned 0 total points
ID: 39917971
I havent exactly found the answer to this problem but I have solved it. The problem lay in the fact that I was performing a standardised rate with confidence intervals in the cube database. It was the confidence intervals that were producing the -1 #IND error for this period. Tracking back through all of the dependent calculations to the source of the data, it turns out that the new data stream lumps all of the over 85 age group into one category rather than divulging numbers for the quinary age bands over the age of 85. As such there are a number of fields containing nulls so by using isnull(quinaryageband, 0) I was able to solve the problem of the whole age group coming out as null.
However why this didnt manifest itself on the old server I will never know. It's a good lesson in never taking anything for granted.
I was assuming that because it gave expected results on the old server there was nothing wrong with the transact SQL in the views stored procs and functions etc that feed the cubes. To me this had to be something to do with the old and new server set up (and in fact there has to be some logical explanation along those lines to explain why it worked on one and not the other). However there was a deeper underlying problem which didnt intially occur to me.
Anyway sorted now so thanks very much anyone who took a look.
0
 
LVL 3

Author Closing Comment

by:trawley
ID: 39931096
Reasons for accepting my solution are contained in the solution itself. Grading myself a 'B' because I still do not understand the reason why I didnt get the -1#IND error on the old server set up in the first place.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why is this different from all of the other step by step guides?  Because I make a living as a DBA and not as a writer and I lived through this experience. Defining the name: When I talk to people they say different names on this subject stuff l…
Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question