Hi, is the IMAGE data on a separate SQL Server instance? Is it contained in a database or a flat file? Need more details...

This may be a little more automated for you 🙂

IF OBJECT_ID('TempDB..#mytable','U') IS NOT NULL

DROP TABLE #mytable

CREATE TABLE #mytable

(CustID varchar(1),ProductName varchar(50),IndexValue1 int, IndexValue2 int, IndexValue3 int)

go

INSERT INTO #mytable(CustID, ProductName, IndexValue1,...

select substring(MyColumnName,charindex(',',MyColumnName)-1,len(MyColumnName))+' '+substring(MyColumnName,1,charindex(',',MyColumnName)-1) from #mytable

1, FN1 LN1

2, Firstname2 Lastname2

3, Fname31 Lastnm3

4, Firstname444 Lastname444

(4 row(s) affected)

Sorry, didn't notice that you wanted the first and last names transposed... 🙂

select top 4 replace(MyColumnName,',','') from MyTable

I think it's a file system permissions issue:

"This is because the SQL Server Service is trying to write the temp DSN to the temp folder for the login that...

Jonathan Kehayias[/url] doesn't agree with you:

'I...

mortalic (7/13/2011)

---

From msdn:

TRUNCATEONLY

Releases all free space at the end of the file to the operating system but does not perform any page movement inside the file....

SQLBOT (7/13/2011)

---

seth delconte (7/13/2011)

---

SQLBOT (7/13/2011)

---

Pretty sure you need to stick with full recovery for mirroring, Seth.

You also don't need to set the recovery model to simple for using dbcc shrinkfile.

In...

Honestly, Seth, unless I'm missing something in your code, I think it's wrong. You don't truncate a log with a regular database backup. A regular database backup only touches the...

SQLBOT (7/13/2011)

---

Pretty sure you need to stick with full recovery for mirroring, Seth.

You also don't need to set the recovery model to simple for using dbcc shrinkfile.

In your script below...

Here's a script I use to shrink the t-logs manually if they stretch too big due to failed backups or something:

--try/catch guarantees that shrink log will not happen if backup...

Is there an error, or is the log just not visibly shrunk?

Have you restored the last transaction log backup on the mirror instance with NO RECOVERY?

http://www.sqlservercentral.com/Forums/Topic683162-146-1.aspx#bm684411

Also, check and see what login accounts your SQL services are using - apparently you need...

How about using a table variable? 🙂

I think you have to have the correct SMO version... the one you want should be here.