My production web site started out as DNN 4.3.5 and upgrated to 4.3.6 and 4.3.7.  I back it up daily with Evotiva's BackupScript. Periodically I do a restore onto my localhost with DNN 4.3.7 Install Kit with a few additional modules & skins for local development and testing. I have done this sever al times sucessfully in the past. I have even upgraded the  localhost install to 4.4.1

Today to tried again. and got an error when restoring the ScheduleItemSettings table. After looking at the tables it was clear that the column sizes in the producting systems (at Godaddy) had changed. They now were: ScheduleID int(4)  --- SettingName nvarchar (100) --- SettingValue nvarchar (4000)

On a virgin 4.3.7 install they are: ScheduleID int(4)  --- SettingName nvarchar (50) --- SettingValue nvarchar (256) and presumeably one of the values in the backup was greater than that size and that is why the script was unhappy.

The only row in the table was for the noghtly schedule of Evotivia's BackupScript.   I presume that if I remove the module and/or  its scheduling the row will go away and I can set the values back to the desired values. 

Anone got an idea about how this corruption coud have occurred?  Did the size of this data change during DNN 4?

--------------------

Actually I just tried and on Godaddy (SQL 2000) I could only reduce them to: ScheduleID int(4)  --- SettingName nvarchar (100) --- SettingValue nvarchar (512) -- My localhost is SQLExpress 2005 so maybe the that has somthing to do with the issue.

I'll no reinstall Evotiva's module and backup again..... 

/DaveS

I hove no modules installed remotely that weren't installed locally. Evotivia's backup script confirmed this because it doesn't create the tables and would have failed if any tables had been created remotely and not locally. The only entry in this table was the settingign for Evotiais script. The only one of any lenght was the its license key.  I just  counted its characters and it is about 12 lines of 50 characters = 600 bytes, so I don't know how it even fit in the original nvchar of 256.  I will talk to them about this.

/DaveS