Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We will be deploying an application with a Postgres back-end and need to provide report writing capabilities in SQL Server. I am exploring options for real-time or near real-time reporting in this environment.

I am curious about linking the Postgres database to our SQL Server environment. Would I be able to build views against the Postgres database that our SQL Server report writers could then use? Are there any additional performance considerations beyond the normal ones? (i.e. views are slower than tables)

share|improve this question
Honestly, we just use our linked servers as sources to pull data into our reporting environment. So we have a nightly job that runs something akin to my answer here and end users report from the Sql Server itself. – swasheck Apr 9 '12 at 17:08
up vote 2 down vote accepted

If you are OK with the reports being run directly off of the Progress database, look into SQL Server Reporting Services and the Report Builder 2.0 in SQL Server 2008 R2. If you can deploy Reporting Services 2012 (part of SQL Server 2012) and you've got SharePoint 2010 installed look into using PowerView so allow people to build reports off of data sets which you've pre-defined as part of a data model.

If you need to get the data into SQL Server then you'll probably want to look at building a SQL Server Integration Services package which would then copy the data from the needed tables into the reporting database on a set schedule.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.