January 10, 2017 at 2:38 pm
Comments posted to this topic are about the item Powershell Script for regular DBA activities
January 11, 2017 at 6:26 am
Pretty nice bit of code, thanks.
January 11, 2017 at 10:02 am
Thanks !!
January 11, 2017 at 12:08 pm
January 11, 2017 at 8:24 pm
This assembly is required to call filesave and folderdialog box via powershell.
Do you latest .net framework installed on your machine ?
January 11, 2017 at 8:27 pm
I use to call this powershell script via batch file.
Here is the code for the batch file
@echo off
powershell -executionpolicy bypass -File C:\Users\mayank\Documents\Powershell\SqlMisc.ps1
pause
Just change the path for the powershell script
January 12, 2017 at 8:26 am
er.mayankshukla - Wednesday, January 11, 2017 8:27 PMI use to call this powershell script via batch file.Here is the code for the batch file@echo offpowershell -executionpolicy bypass -File C:\Users\mayank\Documents\Powershell\SqlMisc.ps1pause
Just change the path for the powershell script
THANK YOU!!!!!!!!
January 14, 2017 at 10:36 pm
Such utilities can be easily used by the developers in the team without making them approach to DBA for such tasks on various development or testing environments.
Who fixes it when either the MDF drive or the backup drive get's filled up? Who fixes it when one developer does a restore over a database of another that has a lot of critical test data in it?
I give my Developers a whole lot of freedom on the Dev boxes but backups and restores won't ever be one of them.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2017 at 5:29 pm
> Who fixes it when either the MDF drive or the backup drive get's filled up?
They can do it them self.
They are all sysadmins, if they can execute those commands.
So, they do not need anybody else to maintain the server.
_____________
Code for TallyGenerator
May 12, 2017 at 9:49 am
Tried to run the script in our environment it gives below error.
Please help to fix it.
Exception calling "Open" with "0" argument(s):
"A network-related or instance-specific error occurred while establishing a connection to SQL Server.
The server was not found or was not accessible.
Verify that the instance name is correct an d that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply