Romain Ferraton

After testing with a longer database name i receive a SQL Server Error ```SQL BACKUP DATABASE [TESTDATABASE_ABC_1eed02d4-f58b-4110-9cee-78c2fa65123a_12345678901234567890123456789012345678901234567890123456789] TO DISK = N'D:\MSSQLBACKUP\MSI\MSSQLSERVER\TESTDATABASE_ABC_1eed02d4-f58b-4110-9cee-78c2fa65123a_12345678901234567890123456789012345678901234567890123456789\Full\TESTDATABASE_ABC_1eed02d4-f58b-4110-9cee-78c2fa65123a_12345678901234567890123456789012345678901234567890123456789_FULL_20240506145012.bak' WITH NOFORMAT, NOINIT, NAME = N'TESTDATABASE_ABC_1eed02d4-f58b-4110-9cee-78c2fa65123a_123456789012345678901234567890-Full Database Backup', SKIP,...

No, i don't agree : the problem occurs before the 259 caracters limits

agree, but with a 229 caracters long (path+filepath) : SQL is working whereas dbatools Backup-DbaDatabase failed

Got it : dbatools add the dbname twice in the path ! even if the token already specify dbname !

My path is ${BackupDirectory}\servername\instancename\dbname\backuptype using -ReplaceInName switch in the Backup-DbaDatabase command. In that case the directory path + filepath length = 229 caracters Unfortunatly Dbatools use ${BackupDirectory}\servername\instancename\dbname\backuptype\\**dbname** in it's path...

Hum... the behavior of the -ReplaceInName is "not correct" and is not possible to build a backup directory hierarchy that "centralize" all the backup types of a database under a...

This problem lead to more frequent backup failures in some cases because of a path too long : "Invalid device name. The length of the device name provided exceeds supported...

I do understand your worries about impacts of such a change, why not adding a new parameter in the Backup-DbaDatabase that will avoid to create a dbname subdirectory : -NoDBSubdir...

No, you have to include an xml file with credentials for each data sources. sample content of the xml file: ` ` Then when you launch the siteimport command add...

If you have embeded datasources yes, but if you have "shared" datasources, only for each "shared" datasources. The xml file is defined here :