January 25, 2011 at 3:25 pm
We have something that does will take care of the any SQL Agent tasks; the real challenge is getting information about setting up a reporting-centric db that is not specific to SSRS.
January 25, 2011 at 3:41 pm
Well in most ways I don't do anything special for SSRS. I try to make the queries as fast as possible, I usually use sprocs to hide the logic from the front-end. Prep for the reports might include pre-calculated/aggregated or denormalized data. I don't really make any distinction for the reporting engine.
I'm a little unsure what you are thinking needs to be done for SSRS that you wouldn't potentially do for any reporting front-end..
CEWII
January 25, 2011 at 3:45 pm
duncfair (1/25/2011)
We have something that does will take care of the any SQL Agent tasks; the real challenge is getting information about setting up a reporting-centric db that is not specific to SSRS.
SSRS is a reporting tool. I regularly liken it to Crystal Reports, a completely different product.
A data warehouse/reporting DB is a structure built to speed OLAP reading, Or Analytical Processing. Compare to OLTP, Transactional Processing. It will denormalize some data, and may go to the extent of Star/snowflake schema.
These are all methods with re-organizing data to make reporting faster. SSRS is a tool most SQL Server people fall back on because, well, hey... it's there and it's free (to us). The engine's already paid for. You're looking to create a reporting/OLAP database. There is no easy method to this. You need to take your existing architecture. You need to then redesign it as an OLAP structure. THEN you need to worry about the data transfer, which will most likely be BCP/Windows Scheduling and then kicking off local procs in the OLAP design to take care of your data upkeep from the staging tables.
I respect that you're attempting to work around the limitations of the 'Lite' edition of SQL Server. What you need to do though is actually review OLAP design for databases, and not worry as heavily about the SSRS component. It's just one of a thousand options. However, around here, it's the one most of us are familiar with.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply