Comments
Sort by recent activity
Just to update this thread v10.2.0.885 released on August 6th appears to have resolved this issue / comments
Just to update this thread v10.2.0.885 released on August 6th appears to have resolved this issue
No worries, glad you guys are still supporting 2000. Trying to get rid of our 2000 instances but 1 or 2 just wont die.
Please can I have a link to the previous version.
Many Thanks / comments
No worries, glad you guys are still supporting 2000. Trying to get rid of our 2000 instances but 1 or 2 just wont die.
Please can I have a link to the previous version.
Many Thanks
Will cross reference the clock skew alert times with the performance on the server and see if there is any correlation. / comments
Will cross reference the clock skew alert times with the performance on the server and see if there is any correlation.
Hi Matt,
Tested this and working as expected now. Tried it on a few different configurations (2005 & 2008, default instance and named instance) and all ok.
Just curious that the fix appears to be in the GUI but the download also updates the agent? ie with the 6.5.0.75 GUI the funcationality works as expected even on 6.5.0.73 agents? Any reason for this.
Many thanks
Andy / comments
Hi Matt,
Tested this and working as expected now. Tried it on a few different configurations (2005 & 2008, default instance and named instance) and all ok.
Just curious that the fix appears to be ...
Just did some more testing.
When I select the create new database radio button the drop down (orginal database data directory) works correctly ie the paths and filenames are correct.
The bug only appears to be when having the overwrite database radio button selected. / comments
Just did some more testing.
When I select the create new database radio button the drop down (orginal database data directory) works correctly ie the paths and filenames are correct.
The bug only a...
I agree with David
When selecting SQL Server Data Directory it should default to the SQL Server settings (specifically it should pick up the log location). [image]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\SQLDataRoot]
=E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
This appears to be missing the final folder \DATA.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\DefaultLog]
F:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA
When chossing original database directory it should be
Database file locations from the database being overwritten. / comments
I agree with David
When selecting SQL Server Data Directory it should default to the SQL Server settings (specifically it should pick up the log location).
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi...
Tried this on a SQL Server 2008 and SQL Server 2005 instance and both have the same issue / comments
Tried this on a SQL Server 2008 and SQL Server 2005 instance and both have the same issue
Tried this on another server (with a default instance) and get exactly the same problem. Ie the filename of the primary file being overwritten with DATA and the file path losing the final folder ie the DATA folder / comments
Tried this on another server (with a default instance) and get exactly the same problem. Ie the filename of the primary file being overwritten with DATA and the file path losing the final folder i...
It looks as if it nearly works.
When selecting Original Database Data Directory it is correctly changing the Transaction Logs path to F:\Program Files\Microsoft SQL Server\....
The problem is the Primary database file path and name (screenshot 2), it changes it to
Path
E:\Program Files\Microsoft SQL Server\MSSQL10.INSTC\MSSQL
File Name
DATA (this is totally wrong and is the end of the folder path)
It should read
Path
E:\Program Files\Microsoft SQL Server\MSSQL10.INSTC\MSSQL\DATA
File name
BGInfo.MDF / comments
It looks as if it nearly works.
When selecting Original Database Data Directory it is correctly changing the Transaction Logs path to F:\Program Files\Microsoft SQL Server\....
The problem is the P...
have recieved the email now / comments
have recieved the email now