Sorry, lots of post here, which error. Also did you make a full backup of these databases before the TL backup? Also why are you doing TL backups on Northwind...

I believe there was a Proc-Blaster Free at one point that was freeware which I downloaded. It is template based (usefull but no major pluses I could see over what...

It is considered best to have the server setup in a situation where viruses cannot occurr. In other words do not run other services and items that can be affected...

This will handle for one database.

SELECT

sysusers.[name] AS UserName,

sysobjects.[name] AS Object,

CASE WHEN xtype IN ('U','V','S') THEN

CASE

WHEN (actadd & 1) = 1 THEN 'Granted'

WHEN (actmod & 1) = 1...

Take a look here and see if any of these KB Articles on the MS KB Site fit you problem. http://search.support.microsoft.com/search/default.aspx?Catalog=LCID%3D1033%26CDID%3DEN-US-KB%26PRODLISTSRC%3DON&Product=sql&Query=dts%2520AND%2520timeout&Queryc=dts+AND+timeout&withinResults=false&srchstep=0&KeywordType=BOOLEAN&Titles=false&numDays=&maxResults=25.

"Don't roll your eyes at me. I will tape them...

Are you viewind this in EM or QA or back thru the ASP page. IF EM or QA I seem to recall an issue with using the ENglish version of...

Sorry to get the effect you are requesting would reuire they be on the same instance of SQL. When they are not then you no long can do this directly....

The best way to force (not actuall enforce) captial letters on is to do UPPER(theirvalue) to do it. With checks you have to do something like so.

MYCOL LIKE '[A-Z][A-Z][A-Z][A-Z]'

and that...

FROM "System Configuration" in BOL

quote:

---

The QUOTED_IDENTIFIER setting determines what meaning Microsoft SQL Server gives to double quotation marks ("). When QUOTED_IDENTIFIER is...

Yes it is never advised to use any kind of relations on a subscribers tables but you can try a few things. (I have not tried this myself sorry, but...

I agree but also for safety do make a standard backup to tape or file and move of the server. And test it on another system before you do anything....

First being both the developer and the DBA can have it's downsides especially if some other developer messes up something that brings down the server that you happened to miss...

Try setting all to manual then start each one independently. Each instance wants to launch a copy of SQL in memory and they may be tying each other up to...

Try

USE dbanme

GO

EXEC sp_change_users_login 'Auto_Fix'

GO

"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

I have never done this before or needed to but the following should work. Create a query task that is executed first with SET IDNITITY_INSERT ON then run the import...