An attempt has been made to use a data extension OLEDB that is not registered for this report se

I am using SQL Server 2005 Express along with the other Express reporting tools (VS Express). I am trying to report against an oracle database. I can design and preview the report however when I attempt to 'deploy' the report to a report server that is on the same machine I am developing on, I get the above error. Is this because I am running an Express version of SQL Server or is this an error?

Thanks,

Sam

Yes, the Express Edition only allows connections to local data sources with a limited set of data extensions. Not all types of data sources are supported in the Express Edition.

-- Robert

An attempt has been made to use a data extension OLEDB that is not registered for this repor

I am using SQL Server 2005 Express along with the other Express reporting tools (VS Express). I am trying to report against an oracle database. I can design and preview the report however when I attempt to 'deploy' the report to a report server that is on the same machine I am developing on, I get the above error. Is this because I am running an Express version of SQL Server or is this an error?

Thanks,

Sam

Yes, the Express Edition only allows connections to local data sources with a limited set of data extensions. Not all types of data sources are supported in the Express Edition.

-- Robert

Alternatives to SQL Server Merge Replication

Hello,

I would like to know what alternatives are avaliable to SQL Server Merge Replication. I am also looking for Third Party Tools. Can anyone name a few for me.

Microsoft supplied alternatives: RDA (Remote data access), ADO.NET Synchronization Services (currentluy in beta), ASP.NET Web Services (rolling your own).|||Is ADO.NET Synchronization Services as powerful as Merge Replication?|||

Just a hunch on why you might be looking for alternatives:

I know many developers are implementing alternatives to RDA and replications in effort to reduce number of CALs required for SQL Server. They believe what if N devices are connected to this “alternative” and “alternative” connects to SQL Server you only need one CAL as there’s only one physical connection to SQL Server. That is, however, not the case and SQL Server EULA has a clause about “through proxy” connection to prevent that scenario so you would need N CALs regardless. If that’s the reason you’re looking for alternatives you might just use RDA/Replication and save time and money on development.

Another reason for alternatives is security –developers don’t want IIS installed as they believe it’s unsecure. If that’s the case I would like to point out IIS has been around for years and runs on millions of hosts around the globe. Thinking self made solution would me more secure is quite perky.

Alternatives to Merge Replication

Hi,

Can anyone help me with third party tools that perform the same way as SQL Servers Merge replication.

What is wrong with Merge Replication?|||

Following is my problem

I am using SQL Server 2000 Merge Replication. Sometimes when the data is replicated there are conflicts which when examined show it is due to voliation of foreign key constraint. But the data (keys) in already present in the master tables. This is so because i think the data in the details table is relpicated first instead of the master table. The conflicts are resolved properly when done using the conflict viewer.

|||

In SQL 2000 you can choose not to replicate foreign key constraints or replicate them and mark them as NOT FOR REPLICATION. See BOL topic http://msdn2.microsoft.com/en-us/library/ms152529.aspx.

In SQL 2005, we have better retry logic as well as article ordering which greatly reduces the need to resolve conflicts if the above doesn't work for you.