Thanks for these URLs. Interesting discussions

AFAIK, you need to restart SQL in order to make these changes for @@SERVERNAME

there's a script on the internet about moving tables between filegroups. This script is able to move files even without clustered indexes (temporary adding clustered indexes)

I used this script to...

make sure, you do a

dbcc updateusage('{databasename}')

and a

sp_updatestats

on your migrated database

Found this answer in BOL:

Although the @@SERVERNAME function and the SERVERNAME property of SERVERPROPERTY function may return strings with similar formats, the information can be different. The SERVERNAME property automatically...

Saw an exact question / solution 2 months ago. Here's the script, but I can't give you the author's name:

SET NOCOUNT ON

SELECT IDENTITY(int, 1, 1) AS agentJobId, name AS agentJobName

INTO...

Check the collation between your database and TempDB. This problem also kicks-in when creating temporary objects

I can't follow you: You're using a function, but you don't want a result from that function. So use a procedure. Use it like

exec {procedurename} @param1=@var, @param2=@var, etc, etc

Or stick...

I assume your clients are Win95 🙂 😀 😛 😉

OK, enough. NT 4 was a product of the 90's. Stop searching for an answer, upgrade your OS. Ever thought...

lazy solution: change job owner to SA

What I've heard is that you need to run CheckDB with DataPurity for migrated databases once. DataPurity is always used for newly created 2005 databases.

Hi,

you can either:

- do a backup/restore or

- do a detach, copy, attach

In both cases, SQL will upgrade you internal databasestructure. Keep in mind that the compatibilitylevel is not changed. Thus...

Update:

I'm also a fan of multiple datafiles, but I'm a little confused when I saw this article:

http://blogs.msdn.com/psssql/archive/2007/02/21/sql-server-urban-legends-discussed.aspx

If you have multiple datafiles, new data will be spread over the datafiles, see this article:

http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/17/948.aspx

Generally, an index scan is faster, because it only contains columns which are indexed (unless it's a clustered index).

Keep in mind that a table scan is not always bad. Especially...