Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««56789

Database Space Capacity Planning Expand / Collapse
Author
Message
Posted Thursday, October 18, 2012 9:23 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, April 18, 2014 8:01 AM
Points: 258, Visits: 701
narayanaswamy (10/18/2012)
Hi All,

In SQL Server 2008 instance i have created spacedm database and created all objects tables,views,sp's

I've executed this command prompt .\write-dbspacetodb.ps1 'instancename' spacedm

I am getting below error from powershell. An exception calling "fill" with "1" can't open database spacedm. Login failed to open Spacedm database

Please help me how to resolve this issue. I have created one login assigned db_owner to spacedm even then same issue.




It seems like you're having trouble making a connection. Try just running a test connection:

$serverName = 'instancename'
$databasename = "spacedm"
$connString = "Server=$serverName;Database=$databaseName;Integrated Security=SSPI;"
$con = new-object System.Data.SqlClient.SqlConnection
$con.ConnectionString = $connString
$con.Open()



Post #1374433
Posted Thursday, January 24, 2013 1:40 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, August 18, 2014 4:41 PM
Points: 1,770, Visits: 3,202
Thanks, Chad, this is one of the best scripts on internet I can find about space monitoring.
I tried serveral before and compare them with this one, this is the cleanest and more powerfull code
and implementation.

Thanks much!
Post #1411330
Posted Thursday, January 24, 2013 6:12 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, August 18, 2014 4:41 PM
Points: 1,770, Visits: 3,202
A question about permissions.
When I schedule the job, because it will run using SQL agent service account, it won't work because it cannot login to other computers using that service account to check disk and db size.
So I created a proxy account using my own credentials, for I am a dba, so I have access to those servers that I need to check.

Is that the right approach to go? I mean for the account that run the SQL job - it has to be sysadmin on all those servers that need to be checked, correct?

Thanks
Post #1411421
Posted Friday, January 25, 2013 5:44 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, April 18, 2014 8:01 AM
Points: 258, Visits: 701
sqlfriends (1/24/2013)
A question about permissions.
When I schedule the job, because it will run using SQL agent service account, it won't work because it cannot login to other computers using that service account to check disk and db size.
So I created a proxy account using my own credentials, for I am a dba, so I have access to those servers that I need to check.

Is that the right approach to go? I mean for the account that run the SQL job - it has to be sysadmin on all those servers that need to be checked, correct?

Thanks


The way I run it--I use an account that has sysadmin rights on servers being collected. I'm not sure if less rights will work easily.



Post #1411642
Posted Friday, January 25, 2013 1:12 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, August 18, 2014 4:41 PM
Points: 1,770, Visits: 3,202
Thanks much.

Does this job have to be scheduled to run daily? How about if I just want to collect the data once a week, or once a month?

If so, do I need to change the view for the column of daily_growth_mb,
because in the view it is like AND d2.dt = DATEADD(dd, - 1, d1.dt)

If I don't change it, and I collect only once a week, then I think it will has no records. correct?

Thanks
Post #1411912
Posted Friday, January 25, 2013 4:54 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, April 18, 2014 8:01 AM
Points: 258, Visits: 701
I haven't looked at the code in a while, but I think you're right on the view.


Post #1411959
Posted Thursday, May 2, 2013 4:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, June 6, 2014 7:55 AM
Points: 6, Visits: 60
Can anyone tell me why the calculation for usable size is (v1.percent_free, v1.size_gb * .8 AS usable_size_gb).

I know it's got to do with the initial disk formating and so forth but why the .8? Something to do with 8 bytes?
Post #1448750
Posted Thursday, May 2, 2013 5:31 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, April 18, 2014 8:01 AM
Points: 258, Visits: 701
An assumption around always keeping at least 20% free space on NTFS volumes.


Post #1448770
Posted Friday, June 21, 2013 1:38 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 29, 2013 1:48 PM
Points: 1, Visits: 106
I removed primary key from dbo.vol_space table because I was getting PK vialotion error. Now I am getting below error. Please help.

ob Name Space Collector
Step Name Write-VolToDb.ps1
Duration 00:00:04
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user:. The job script encountered the following errors. These errors did not stop the script: A job step received an error at line 51 in a PowerShell script. The corresponding line is ' Get-WmiObject -computername "$ComputerName" Win32_Volume -filter "DriveType=3" | '. Correct the script and reschedule the job. The error information returned by PowerShell is: 'Invalid class ' A job step received an error at line 52 in a PowerShell script. The corresponding line is ' foreach { add-member -in $_ -membertype noteproperty UsageDT $((Get-Date).ToString("yyyy-MM-dd")) '. Correct the script and reschedule the job. The error information returned by PowerShell is: 'Cannot bind parameter because parameter 'InputObject' is specified more than once. To provide multiple values to parameters that can accept multiple values, use the array syntax. For example, "-parameter value1,value2,value3". '. Process Exit Code -1. The step failed.
Post #1466374
« Prev Topic | Next Topic »

Add to briefcase «««56789

Permissions Expand / Collapse