Comments
Sort by recent activity
Hi Eddie
Thanks for the response.
Once the restore failed, I took another backup and copied that across again, but it also failed. So it may have been a corrupt copy, but it's a coincidence that the Windows copy would corrupt the file twice.
I also tried to restore a converted native version of the file, but did not take a native backup and try that.
Because of the size of the database, it became a bit tedious to try too many options, so we resorted to detaching, copying and re-attaching the database and that worked fine. So the copied version of the backup has subsequently been deleted so no comparison can be done.
I'll have to get hold of you if I get this problem again in the future.
Regards
Brad. / comments
Hi Eddie
Thanks for the response.
Once the restore failed, I took another backup and copied that across again, but it also failed. So it may have been a corrupt copy, but it's a coincidence that th...
Hi Brian
I'm not sure that will help as the SQL Compare Pro is installed on one machine and there are a handfull of Windows 2003 Servers running SQL Server that will call this .exe over the network.
What is it exactly that you are suggesting I copy?
Thanks
Brad. / comments
Hi Brian
I'm not sure that will help as the SQL Compare Pro is installed on one machine and there are a handfull of Windows 2003 Servers running SQL Server that will call this .exe over the network...
THE ANSWER ....
Hi Brian
I got the answer. .NET doesn't like running .exe's over the network because of trust issues, so to solve this do the following:
On the server you want to call the remote .exe from ....
Go to Start > Programs > Admin Tools > .NET Configuration ...
then to Runtime Security Policy > Machine > Code Groups > All Code ...
> Then create a new group.
> Make the condition type "URL"
> Make the URL [url=file://machine_hosting_exe_name/*]file://machine_hosting_exe_name/*[/url]
> Set the permissions to "Full Trust"
And there you go - everything run from the hosting machine will be allowed. You can obviously narrow it down to only allow your exe etc.
Cheers
Brad / comments
THE ANSWER ....
Hi Brian
I got the answer. .NET doesn't like running .exe's over the network because of trust issues, so to solve this do the following:
On the server you want to call the remote .e...
Aah ... that is not ideal. I was hoping it would be included in the list of objects that are compared.
Oh well, maybe in a later release they can be separated.
Thanks alot. / comments
Aah ... that is not ideal. I was hoping it would be included in the list of objects that are compared.
Oh well, maybe in a later release they can be separated.
Thanks alot.