Viewing 15 posts - 1,141 through 1,155 (of 1,318 total)
I had this problem the other day because of an issue with the domain controller (i.e. it wasn't specifically a SQL Server issue).
February 26, 2014 at 3:25 am
- Are you on RTM or have you applied any service packs?
- Do the databases have valid owners? Check using
SELECT suser_sname( owner_sid ), * FROM sys.databases
February 25, 2014 at 9:58 am
Sorry- another double post. I would get your networks guys involved.
February 25, 2014 at 9:51 am
Have you asked your networks guys if anything happened around that time?
February 25, 2014 at 9:30 am
As SQLRUNNR says, the error message is quite straightforward; you already have a database with that name. Were you wanting to restore it rather than to attach it?
February 25, 2014 at 9:29 am
Is your .NET 3.5 Framework still installed, etc?
February 24, 2014 at 8:49 am
Have a look at this link and see if it helps.
February 21, 2014 at 9:00 am
I think what MysteryJimbo was saying was we don't know if your migration can be broken down because we don't know anything about it, and the information you've given us...
February 21, 2014 at 7:34 am
TerrenceTheCat (2/21/2014)
1. The differential LSN was broken by the hourly full backups that were taken without the "with copy"
Has this been resolved now?
My concern is realistically within the teams...
February 21, 2014 at 3:47 am
Viewing 15 posts - 1,141 through 1,155 (of 1,318 total)