Code must be profiled so if this is development server you either do the job or ask for developer edition from IT for the developers because even in software engineering...

Management can change that for you but you could affect productitivity so you first task is to create a copy of the database and make relevant changes and create a...

You need to give them the developer edition it is under $50 online because Profiler uses a lot of memory so it is best run on the developer and test...

I think here is how you find out what to do but I could be wrong because I am on the logical end.

https://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/10/625659.aspx

The error is related to compatibility mode 80 of your upgraded database your developer may have used .NET 2.0 decimal which may not map to SQL Server 2000 decimal. ...

These are in the physical index architecture check below for details from the owners of the relational engine.

http://blogs.msdn.com/sqlserverstorageengine/archive/2006/07/08/under-the-covers-gam-sgam-and-pfs-pages.aspx

I think most SSAS permission are derived from Windows but here are user permissions you can define and base permissions.

http://technet.microsoft.com/en-us/library/ms175408.aspx

http://technet.microsoft.com/en-us/library/ms174786.aspx

The short answer is no the long answer either use SSRS 2008 or use the for pay VS2008 and use the free Asp.net or Winform version which is free.

http://blogs.msdn.com/alexgor/archive/2008/11/07/microsoft-chart-control-vs-dundas-chart-control.aspx

The first line of your stack trace tells me it is Asp.net and I have posted two Asp.net solutions so do all that...

Here are two possible reasons for the error and fixes per Microsoft, if these are not relevant to you post again but this time I need to know Asp.net version...

Try the two links below before you buy any book look at existing code and samples before you buy a book. There are many code sample relevant info on...

I think you have not installed the Native Client driver so download install it and reference the x86 verson of it so you can connect to x86 2000 and 2005.

http://www.microsoft.com/downloads/details.aspx?familyid=c6c3e9ef-ba29-4a43-8d69-a2bed18fe73c&displaylang=en&tm

well during some point in this process a new file was created on my C: drive under C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\FTData. the file name is the same as my database...

The most likely reason for such issues is installing SSRS in other drive because Microsoft require the configuration path to be fixed that is install in C drive.

The other is...

If this is a production site and it gets very busy you will run into issues because when a SQL Server component comes with fixed path it usually needs operating...