Reputation
865
Top tag
Next privilege 1,000 Rep.
See vote count; VIP usercard
Badges
1 12 24
Impact
~73k people reached

  • 0 posts edited
  • 0 helpful flags
  • 31 votes cast
8h
awarded  Popular Question
Apr
21
awarded  Famous Question
Mar
13
awarded  Popular Question
Mar
1
awarded  Yearling
Feb
10
awarded  Nice Question
Jan
6
awarded  Notable Question
Nov
11
awarded  Popular Question
Sep
23
awarded  Notable Question
Aug
4
awarded  Notable Question
Jul
16
awarded  Popular Question
Jul
2
awarded  Inquisitive
Jul
2
awarded  Curious
Jul
2
awarded  Notable Question
May
29
accepted SQL Server FILELISTONLY command providing incorrect logical database name
May
29
comment SQL Server FILELISTONLY command providing incorrect logical database name
Found it!!! This is where having the backup file would have helped you I'm sure. The backup file contains multiple backups. So the FILELIST command the way that I'm using it is pulling the earliest backup logical file name. which is not the logical file name associated with the backup I'm trying to restore.
May
29
comment SQL Server FILELISTONLY command providing incorrect logical database name
Gotcha but in this case wouldn't the backup file have gotten the designation from sys.master_files?
May
29
comment SQL Server FILELISTONLY command providing incorrect logical database name
By that command I mean the ALTER DATABASE x MODIFY FILE (name = 'y', newname = 'z'); command.
May
29
comment SQL Server FILELISTONLY command providing incorrect logical database name
@AaronBertand - I just wanted to take a moment and say thanks for your persistence in helping me with this problem. I really appreciate it. - I can use that command to set them to 423 which would allow the procedure to go forward but when I change them back it doesn't change the value coming back from filelist. Where does filelist pull this information from? The logical file is correct in sys.master_files.
May
29
comment SQL Server FILELISTONLY command providing incorrect logical database name
Yep Sorry about the file names. They are actually all 4 digit numbers (and we have 3000 of them) for reasons that predate me. were working on fixing that. If I were to use Modify file on these databases now to make the logical names match the physical names is that likely to fix the issue do you think?
May
29
comment SQL Server FILELISTONLY command providing incorrect logical database name
@AaronBertrand - since the front of the house can use that stored procedure to create databases from "template databases" ie just another db. and then use those new databases to create other databases I can't tell. I suspect that database 423 is in database 4295's ancestry at some point. Did that make sense?