Viewing 15 posts - 76 through 90 (of 136 total)
One option is to pass an array in and then split it and search based on the values resulting from that.
But I'd probably use a table valued parameter.
October 17, 2017 at 10:32 am
...
The end result set I am hoping to look like
job_name
failure_count
last_outcome
last_rundate (optional)
As always any...
October 17, 2017 at 8:30 am
I did test this with SSMS, I didn't find that I need to be...
October 17, 2017 at 7:51 am
October 12, 2017 at 8:30 am
Have you tried putting your connection in the database first? Either with a USE statement or changing your Invoke-Sqlcmd -Database parameter to specify the appropriate database instead of 'master'.
October 12, 2017 at 8:24 am
Lately I've been doing a no-cheese pizza with pepperoni, bacon, canadian bacon, chicken, sausage, and roasted green chile. Without the cheese it's basically a spicy, meaty flatbread. Dairy and I...
October 12, 2017 at 8:06 am
October 12, 2017 at 8:00 am
No, its not an index maintenance, because this procedurs running only Sunday.
October 12, 2017 at 7:46 am
I only need high id's and dates if there anything...
October 11, 2017 at 8:08 am
I believe 2016 Standard has a smaller set of auditing options than Enterprise, but Database Audit Specification is still supported. I'm currently running it on one database on a 2016...
October 11, 2017 at 7:41 am
Currently bitbucket. Last place I was at used perforce or github (depending on which group you were talking to) and before that TFS. Perforce never worked as well as TFS...
October 10, 2017 at 12:18 pm
You're just using the CREATE LOGIN statement? I get as far as verifying that the user got created with hasaccess=0, but when I run CREATE LOGIN it always kicks back...
October 10, 2017 at 9:42 am
Maybe a silly suggestion since improper reporting of the database connection isn't supposed to be an issue anymore, but have you tried re-opening SSMS and pasting the stored procedure code...
October 10, 2017 at 9:20 am
Viewing 15 posts - 76 through 90 (of 136 total)