179 reputation
9
bio website
location San Diego, CA
age 49
visits member for 2 years, 5 months
seen Sep 25 at 23:53

SQL Server database engineer ( MCSE: Data Platform )


Sep
24
awarded  Autobiographer
Jun
30
awarded  Self-Learner
Apr
29
answered '+' operator with one operand!
Dec
8
revised Using SQL Server SMO with a Port number
Added note regarding enabling TCP/IP connections to SQL Server
Dec
7
answered Using SQL Server SMO with a Port number
Dec
6
awarded  Quorum
Nov
26
comment PowerShell to get database schemas
What's the scope of this question? Do you need help with XML in any way, or is that just background? When you say "I want to get all "schemas"", do you just need a list of the schema names from a database? Or, do you want to access objects within each schema in the database? If so, what do you want to do with the database schema objects?
Nov
22
revised Need for indexes on foreign keys
Added another helpful link
Nov
22
answered Need for indexes on foreign keys
Nov
21
revised SQL Server, how to execute a job against all databases on server?
added 285 characters in body
Nov
21
revised SQL Server, how to execute a job against all databases on server?
added 227 characters in body; discovered that "SELECT at_at_SERVERNAME" is enough to break the edit commit
Nov
21
answered SQL Server, how to execute a job against all databases on server?
Nov
13
awarded  Popular Question
Nov
12
awarded  Supporter
Oct
24
answered Does failed task considered to be run to completion in SQL Server maintenance plan terminology?
Oct
22
accepted SQL Server 2012 SQL Agent Job with PowerShell step fails on Out-File cmdlet with “ReportWrongProviderType” error
Oct
22
answered SQL Server 2012 SQL Agent Job with PowerShell step fails on Out-File cmdlet with “ReportWrongProviderType” error
Oct
22
comment SQL Server 2012 SQL Agent Job with PowerShell step fails on Out-File cmdlet with “ReportWrongProviderType” error
Adding a try/catch block, I captured the error output: A job step received an error at line 28 in a PowerShell script. The corresponding line is ' throw $e'. Correct the script and reschedule the job. The error information returned by PowerShell is: 'System.Management.Automation.CmdletInvocationException: Cannot open file because the current provider (SqlServer) cannot open a file. The account running the job has Full Control of the target directory. Perhaps there is a missing permission that would allow Powershell to act on a file share in Win2012?
Oct
22
comment SQL Server 2012 SQL Agent Job with PowerShell step fails on Out-File cmdlet with “ReportWrongProviderType” error
I've updated the question text with the operating system version change. I ran the job with the ErrorVariable as suggested, however the error message text remained the same, even after setting $ErrorActionPreference = 'Continue'.
Oct
22
awarded  Editor