anthony.green (3/19/2012)

---

how are you licensing the servers? CPU lics or Server&CAL lics?

if CPU then you only need to purchase the amount of Enterprise licences which match the number of...

anthony.green (3/19/2012)

---

i've done this in the past when consolidating hardware, there are no issues with it as the binary files are installed in different folders, the only limitation we had...

saidapurs (2/7/2012)

---

Hi,

How many tables you are truncating, like if you ave five table very large then export the data than delete from table subscribe it then...

Worked this around by putting the script into the text file and running this from the job step:

c:\temp\DSM.ps1

Everything works now, but it would be interesting to find out how to...

azdzn (1/12/2012)

---

Here it is :

param ( [string]$ComputerName = "." )

Get-WmiObject -computername "$ComputerName" Win32_LogicalDisk -filter "DriveType=3" | foreach {

add-member -in $_ -membertype noteproperty UsageDT $((Get-Date).ToString("yyyy-MM-dd"))

add-member -in $_ -membertype...

Anyone? :unsure:

It seems like this fixed the previous error,...

It seems like this fixed the previous error, but when I try to put it into a job step, the job fails with this error message:

Unable to start execution of...

Tried different things, coming closer now:

$serverName = "MyServer"

$databaseName = "DBMonitor"

$Connection = New-Object System.Data.SQLClient.SQLConnection

$Output = New-Object WMISearcher

$Connection.ConnectionString ="Server=$serverName;Database=$databaseName;trusted_connection=true;"

$Connection.Open()

$Command = New-Object...

Dev (11/16/2011)

---

Yes you can but with some limitations.

Using FILESTREAM with...

I was also thinking of using filestreaming to store the nvarchar(max) values on the file system. This should fix the memory issue, as the buffer cache is not used...

Gianluca Sartori (11/15/2011)

---

Roust_m (11/14/2011)

---

Hi,

They are going to put a lot of records with nvarchar(max) values into a table (around 3 million). The table will grow from 3GB to 300GB...

Found the solution, if someone else would ever need it:

$timestamp = (get-date).AddDays(-1);

$timestamp = date $timestamp -format yyyy-MM-dd

$DBScriptFile = "\\MyServer\Scripts\MyDb\08_SPs " + $timestamp + ".sql"

Invoke-Sqlcmd -ServerInstance localhost -database...

Found it out:

$timestamp = (get-date).AddDays(-1);

$timestamp = date $timestamp -format yyyy-MM-dd

TZ.DBGeek (11/1/2011)

---

Have you tired the -v parameter in sqlcmd in combination with using another environment (like Powershell) to do the date calculation and set it to a variable to then...