Just use advanced search (ctrl-f) and enter the same field (in your case the id) three times.
Enter the numbers and you have your wanted search results.
- Edited by Patrick Wahlmüller 21 hours 39 minutes ago
Just use advanced search (ctrl-f) and enter the same field (in your case the id) three times.
Enter the numbers and you have your wanted search results.
- Edited by Patrick Wahlmüller Wednesday, July 22, 2015 9:37 AM
Just use advanced search (ctrl-f) and enter the same field (in your case the id) three times.
Enter the numbers and you have your wanted search results.
- Edited by Patrick Wahlmüller Wednesday, July 22, 2015 9:37 AM
Just use advanced search (ctrl-f) and enter the same field (in your case the id) three times.
Enter the numbers and you have your wanted search results.
- Edited by Patrick Wahlmüller Wednesday, July 22, 2015 9:37 AM
Just use advanced search (ctrl-f) and enter the same field (in your case the id) three times.
Enter the numbers and you have your wanted search results.
- Edited by Patrick Wahlmüller Wednesday, July 22, 2015 9:37 AM
Just use advanced search (ctrl-f) and enter the same field (in your case the id) three times.
Enter the numbers and you have your wanted search results.
- Edited by Patrick Wahlmüller Wednesday, July 22, 2015 9:37 AM
There is the community driven and built SMlets for PowerShell. They are crazy useful, but given the community nature of them the only support you'll get is TechNet or other blogs. Not a criticism by any means, they are wildly valuable and necessary just always worth caveating that.
They are available here on CodePlex.
Granted - no GUI as you mentioned, but just had to throw it out there. As far as backend database, I think most would agree touching the production Service Manager database is something you should try to avoid in all scenarios. However, if you are SQL willing/able you could construct some SSRS reports for your SCSM Data warehouse and that way they are available in the console? Sure you'll have to edit in Report Builder, but at least you'll have the easy front end available. Granted, it's a slight misuse of reporting...but I'm just typing outloud
Linking to the backend DB Server is possible, but I do not recommend this for end users, but I do query the database directly.<o:p></o:p>
You need to have SQL skills, since there is a table for each Workitem and a relationship table, with relationships in it. So it is not easy, not recommended, but possible.<o:p></o:p>
One thing @ security: Its maybe saver to give an SQL read only account to an end user than to give him powershell cmdlets.
- Edited by Patrick Wahlmüller 17 minutes ago
Linking to the backend DB Server is possible, but I do not recommend this for end users, but I do query the database directly.
You need to have SQL skills, since there is a table for each Workitem and a relationship table, with relationships in it. So it is not easy, not recommended, but possible.
One thing @ security: Its maybe saver to give an SQL read only account to an end user than to give him powershell cmdlets.
- Edited by Patrick Wahlmüller 6 minutes ago
Linking to the backend DB Server is possible, but I do not recommend this for end users, but I do query the database directly.
You need to have SQL skills, since there is a table for each Workitem and a relationship table, with relationships in it. So it is not easy, not recommended, but possible.
One thing @ security: Its maybe saver to give an SQL read only account to an end user than to give him powershell cmdlets.
- Edited by Patrick Wahlmüller Friday, July 24, 2015 7:08 AM
Linking to the backend DB Server is possible, but I do not recommend this for end users, but I do query the database directly.
You need to have SQL skills, since there is a table for each Workitem and a relationship table, with relationships in it. So it is not easy, not recommended, but possible.
One thing @ security: Its maybe saver to give an SQL read only account to an end user than to give him powershell cmdlets.
- Edited by Patrick Wahlmüller Friday, July 24, 2015 7:08 AM
Linking to the backend DB Server is possible, but I do not recommend this for end users, but I do query the database directly.
You need to have SQL skills, since there is a table for each Workitem and a relationship table, with relationships in it. So it is not easy, not recommended, but possible.
One thing @ security: Its maybe saver to give an SQL read only account to an end user than to give him powershell cmdlets.
- Edited by Patrick Wahlmüller Friday, July 24, 2015 7:08 AM
Linking to the backend DB Server is possible, but I do not recommend this for end users, but I do query the database directly.
You need to have SQL skills, since there is a table for each Workitem and a relationship table, with relationships in it. So it is not easy, not recommended, but possible.
One thing @ security: Its maybe saver to give an SQL read only account to an end user than to give him powershell cmdlets.
- Edited by Patrick Wahlmüller Friday, July 24, 2015 7:08 AM
Linking to the backend DB Server is possible, but I do not recommend this for end users, but I do query the database directly.
You need to have SQL skills, since there is a table for each Workitem and a relationship table, with relationships in it. So it is not easy, not recommended, but possible.
One thing @ security: Its maybe saver to give an SQL read only account to an end user than to give him powershell cmdlets.
- Edited by Patrick Wahlmüller Friday, July 24, 2015 7:08 AM
Linking to the backend DB Server is possible, but I do not recommend this for end users, but I do query the database directly.
You need to have SQL skills, since there is a table for each Workitem and a relationship table, with relationships in it. So it is not easy, not recommended, but possible.
One thing @ security: Its maybe saver to give an SQL read only account to an end user than to give him powershell cmdlets.
Is this documented anywhere how to do this? I've got SQL skills. I know what the Server Name connection string is in Service Manager but is that the same name as the backend SQL Server? Thank you
As Anton writes: Direct SQL is not supported and I would never give these possibilities to our endusers.
Said that: You'll have to ask your admin, where the SQL server is, since we can not know your Environment. And you'll have to ask, if you get rights there.
- Edited by Patrick Wahlmüller 1 hour 34 minutes ago
As Anton writes: Direct SQL is not supported and I would never give these possibilities to our endusers.
Said that: You'll have to ask your admin, where the SQL server is, since we can not know your Environment. And you'll have to ask, if you get rights there.
- Edited by Patrick Wahlmüller Tuesday, July 28, 2015 5:42 AM
As Anton writes: Direct SQL is not supported and I would never give these possibilities to our endusers.
Said that: You'll have to ask your admin, where the SQL server is, since we can not know your Environment. And you'll have to ask, if you get rights there.
- Edited by Patrick Wahlmüller Tuesday, July 28, 2015 5:42 AM
As Anton writes: Direct SQL is not supported and I would never give these possibilities to our endusers.
Said that: You'll have to ask your admin, where the SQL server is, since we can not know your Environment. And you'll have to ask, if you get rights there.
- Edited by Patrick Wahlmüller Tuesday, July 28, 2015 5:42 AM
As Anton writes: Direct SQL is not supported and I would never give these possibilities to our endusers.
Said that: You'll have to ask your admin, where the SQL server is, since we can not know your Environment. And you'll have to ask, if you get rights there.
- Edited by Patrick Wahlmüller Tuesday, July 28, 2015 5:42 AM
As Anton writes: Direct SQL is not supported and I would never give these possibilities to our endusers.
Said that: You'll have to ask your admin, where the SQL server is, since we can not know your Environment. And you'll have to ask, if you get rights there.
- Edited by Patrick Wahlmüller Tuesday, July 28, 2015 5:42 AM
This topic is archived. No further replies will be accepted.
Other recent topics
