Minaz Amin (12/14/2012)
I will check the link.
Also Iam trying to using paramter in the datasource but it failed with the following error. Almost broken
but every run the same error popups
Parameterized datasource with server and database as parameter text type.
=”datasource=” &Parameters!Server.Value&;initialcatalog=” &Parameters!Database.Value
The ConnectString expression for the data source ‘DataSource1’ contains an error: [BC30037] Character is not valid.
The way I've implemented my solution is like this:
1) I used a dedicated utility server which has SQL Server Database Engine, SSIS and SSRS installed on it.
2) Then I created a DBA Repository database (this just hold information about jobs, backups, users, db sizes etc....)
3) The SSIS package runs every day in the morning and uses a servers table in my repository database to loop through the servers. There is logic to handle domain and non-domain servers.
4) I then created my SSRS reports with my data source pointing at the repository database.
So if you can work out the following for me then we'll take it from there:
1) How many SQL instances are you going to monitor?
2) Are they all in the same domain?
3) Where do you plan to store the gathered information?
It takes a minimal capacity for rational thought to see that the corporate 'free press' is a structurally irrational and biased, and extremely violent, system of elite propaganda. David Edwards - Media lens
Society has varying and conflicting interests; what is called objectivity is the disguise of one of these interests - that of neutrality. But neutrality is a fiction in an unneutral world. There are victims, there are executioners, and there are bystanders... and the 'objectivity' of the bystander calls for inaction while other heads fall.Howard Zinn