We have recently upgraded our server from 2012 to 2014 and I am noticing some strange behaviour - can anybody point me in the right direction?Scenario (the names have been changed to protect the innocent):We have two instances of SQL on one server - both running at level 12.0.4100. These instances are called SQLDB1 and SQLDB2.SQLDB1 contains the production databases - for this example we will say there is one database called [b]Production[/b]. Data file is called Production.mdf and log file called Production.ldf. The data files for [b]Production [/b] are on drive D: for data and L: for log files. Logshipping has been set up to [b]ReportProduction[/b] on SQLDB2. The data and log files for [b]ReportProduction[/b] are on drive R:, with the data file called ReportProduction.mdf and the log file called ReportProduction.ldfWhen I run the following script on each instance, the physical file details are shown correctly for both databases.[code="sql"]SELECT sd.NAME ,smf.NAME ,smf.physical_name ,(CONVERT(DECIMAL(32, 2), smf.size) * 8096) / (1024 * 1024 * 1024) AS SizeGBFROM sys.master_files smfINNER JOIN sys.databases sd ON sd.database_id = smf.database_idLEFT JOIN sys.database_mirroring dm ON sd.database_id = dm.database_idWHERE 1 = 1 AND sd.database_id > 4 AND sd.NAME LIKE '%Production%'ORDER BY sd.NAME ,SizeGB DESC[/code]When I right click on the [b]ReportProduction [/b]database on SQLDB2 in SSMS and choose properties/Files. it shows the details of the files fro the [b]Production [/b]database, not the [b]ReportProduction [/b]database - ie data file on D:, Log file on L:, and the physical name as that of the Production database. The database properties show the same on the SQLDB1 instance.Has anyone any idea why this is happening?
↧