Scan multiple instances on one SQL server

if you have a SQL server with multiple instances, the only way possible right now to scan all of them with the "Easy Connect SQL" scan is to add some DNS aliases because you can scan one servername only one time.

This is very awkward to handle. It would be much better to add a server once and be able to scan all instances.

Find more posts tagged with

arm

scan

sql

instance

Status: None

Comments

allmecht

You can use this notation in the connection string:

Data Source=somesqlserver\instancename;Initial Catalog=msdb;Integrated Security=false;User Id=<scanUser>;Password=<password>;

No need to use DNS aliases.

It's compulsory to add each instance as a separate scan. An instance is a separat installation of a sql server.

MichaelFink1

but my customer has maaany servers and many instances on them and wants to minimize the effort.

I know that as far as SQL is concerned they are different servers.

allmecht

1. your customer thinks sql server instances are like file shares, which they are not,

2. Easy Connect SQL scans ONLY the sql server on this server, not the server itself,

3, to achieve this a new backend has to be implemented, the backend has to scan the underlying OS for installed SQL server instances,

4. it's just a bit of diligence

MichaelFink1

i know all that, but it would be more convinient if we could scan all instances with just one scan. Of course with an option to except some instances, its not always the case to scan all.