There is no database connector for SQL, yes that is a pain, feel free to raise a feature request or an idea for it.
Workaround: if it is SCCM or Discovery then there are native connectors for everything else you need to either use an API integration or if it is SQL Server we usually write SSIS (SQL Server Integration Package) packages to extract the information to a CSV file or xml and then import for a shared folder (or FTP/SFTP if SaaS). The SSIS export can be scheduled and the import to ISM scheduled to a frequency that suits (hourly for example depending on the data refresh frequency)
I hope that helps, if you get stuck just ask here and someone will help out.
Thank you for replying this.
I agree that using SSIS package can be a workaround but from my experience, not all customers accept this method and found it heavy to maintain
Each time they need to add an attribute, they have to edit SQL view and edit SSIS package and export it again
Also they have to manage concurrent access (and security aspects) for CSV files when exported files are used by more than one application (If an application use the file, this will be locked and interrupt the other import, so they have to schedule each one or export in different folder destination)
Have you an idea how SaaS customer manage this case ? I suppose that API is the best solution because using a shared folder seems to be complicated.
Thank you very much
SaaS customers use manual uploads, ftp/sftp sites and API connections. Depends on the resources the customer has and if the upload if a one off or not.