sql server reporting services: Shared DSN -- sql server reporting services

Shared DSN

rschiefelbein NO[at]SPAM aimhealth.com
2/13/2006 2:09:05 PM

sql server reporting services:

Can anyone give insight between Shared vs. NonShared DataSources in SQL
Server Reporting Services 2005 and it being problematic? We have
created a folder that contains one DataSource per server\database and
we point all reports to the appropriate DataSource. For example, if we
have 5 reports that all utilize the STUFF database on our PROD server
then we have create 1 STUFF DataSource. Then all 5 reports use this 1
DataSource.

My question is this: Are there any issues that would arise from doing
this when we have a large number of concurrent users? Could this
present a bottleneck in any way for Reporting Services?

Thanks

Ramona

RE: Shared DSN

Wayne Snyder
2/14/2006 5:30:20 AM

NO, there are no concurrency issues, since this doesn't imply any particular
limitation on connections, it is just sharing the connection information..

We consider it a best practice to do exactly what you are doing, and require
it of our projects...

--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC

I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server reporting services group.