Kiara (11/4/2011)

Yup. But when I've been testing, they seem to do less r/w activity than temp tables do. Could just...

Lynn Pettis (11/3/2011)

Now that we have moved data from B to A, there is more that needs to be done that we didn't tell you.

Come on people,...

Try connecting with the DAC port like this

sqlcmd –S127.0.0.1,1434

How does your setup compare to the following example?

http://blog.sqlauthority.com/2008/08/23/sql-server-2008-configure-database-mail-send-email-from-sql-database/

What is the OS?

Have you confirmed that you are using the correct mail server address?

Nan82 provided the easiest way to do this. Verify that your table is defined exactly the same between the old source and the new source and you should be...

Sounds like your mail server is configured to require secure authentication.

Can you script out your database mail profile and verify your settings with the Exchange admin?

Retry the above but try this

NET START MSSQLSERVER /c /f /T3608

Use t3608 instead of 3508

Then try the DAC connection (you may need to look up your dac port)

sqlcmd -S tcp:127.0.0.1,<DAC...

Congrats

L' Eomot Inversé (11/3/2011)

Sit-in

Is that new path for tempdb valid?

Next option might be to try the DAC - dedicated administrator connection

Try this:

(a) From command prompt type sqlservr -c -f

(b) then try

C:\>SQLCMD -q"Alter database tempdb modify file (name = tempdev, filename = 'Y:\SQL\tempdb.mdf')"

GO

C:\>SQLCMD -q"Alter database tempdb modify file (name = templog,...

Because it (what the developer did) resyncs the metadata. That is what has happened here.

Try starting in minimal config (SQL Server), and then altering the paths to the correct paths.

sqlservr.exe -f

Here's a similar thread

http://www.sqlservercentral.com/Forums/Topic545301-146-1.aspx