- maybe you may also want to migrate the most critical objects to a new filegroup, so they will not be influenced that much at shrink time.

- shrinking is done...

use IDENT_CURRENT( 'table_name' )

the "database project" icon is not in the same group as the Integration server or report server icon (Business Intelligence Projects), but you can find it in the "visual basic"...

Switch your SSMS settings to SQLCMD and you'll get a whole bunch of new statements available.

SSMS Query pane

tabl Query --- choose SQLCMD mode

:connect yyyyy

is the statement you're looking...

- did you check the replace statement ?

- maybe a function replacing them would serve you better (in stead of having to code it every single time over and again)

...

Welcome 😉

Indeed when googling the web many solutions go about clr-debugging.

For debugging an tsql-sproc with VS2005 (bi devstudio2005) ..

Don't use the CLR way !

Just:

- create a new db project

then

-...

- I'm told Xcopy should go faster than copy

- also first delete your old backup at the destination and copy the file afterward.

- There are solutions the can compress your...

there is off course the free SQL Server Migration Assistant for Access (SSMA Access)

http://www.microsoft.com/sql/solutions/migration/access/default.mspx

you could use the sp_msforeachdb (undocumented !! :ermm: )

Check SSC for some examples ....

http://www.sqlservercentral.com/Forums/Topic307978-146-1.aspx#bm309930

- IMO referencing tables should reside on the same database for consistency and/or unit of recovery.

If you did split for performance reasons(split files), check out using filegroups....

more on SPN-info

http://technet2.microsoft.com/windowsserver/en/library/b3a029a1-7ff0-4f6f-87d2-f2e70294a5761033.mspx?mfr=true

make sure you can see the server registered with the actualy used portnumber ! (be carefull with dynamic ports !)

We try to avoid these huge errorlog files by cycling them at least every week.

On our new servers the default is to cycle on a daily basis and keeping...

So exec Sp_Cycle_ErrorLog or dbcc errrorlog do not work using Query analyser.

Did you also perform a checkpoint using Query analyser ?

If none of the above work, I guess you're...

Books online explains it !

A user can set a savepoint, or marker, within a transaction. The savepoint defines a location to which a transaction can return if part of the...

no !

Savepoints only work within your transaction.

(check BOL)

You'll need to search for other solutions to minimize your locking elaps time.

- Try to optimize setbased handling of your data.

- AVOID cursors

-...