I noticed that after the migration yesterday, we could no longer connect to our databases via Visual Studio. After submitting a ticket, I was told that there is no current solution to this and we will have to create local databases and simply give you the backup files to restore. This is completely unacceptable.
We have dozens of client projects in development that connect to the MSSQL12 databases and our team is making constant changes to their design and functionality. You can’t expect us to provide your team with multiple backups per day with no idea how fast or when they will be uploaded.
The migration should not have been done if you guys did not have a workaround in place. I am now stuck with our clients because they are expecting to see changes within the next couple of hours, and I have to have our team spend time creating local databases, and then submitting them to you to restore. I am completely frustrated with Jodo as a whole and can’t believe this was handled so poorly.
What is the timeframe for a workaround to be implemented?
It is already done.
It was working via old IP the entire time as well (since fixing the traffic making the redirector crash), the old IP worked on port 1433 without even any extra port. That won’t last forever, but the new one is the solution for it for the long term.
Hi, I have to say that the blocking of outside-datacenter-sql-access was communicated through the forums last months… So shouldn’t be new for any active customer/reseller.
I warned all my clients that internet mssql connectivity would be lost after migration, and that a workaround for direct access would come available, but for nobody I made a guarantee nor a gave date for this.
What the guys at Jodo can improve is that they make a upfront planning available, or update the target-dates at the status.jodohost.com site, to give us clients/resellers more time to issue warnings to our clients. From what I have seen dates are only being filled when migration is ready to start.
Regards, JP
I’m hoping you can help me then since the person that answered my ticket (ORV-11474-796) has no idea and the person in chat “Krishna” didn’t know either. We’ve always connected to our databases through data connections in Visual Studio using the server name mssql12.bassodesigngroup.com and the username and password for the database we need to access. This is no longer working. What server name do I have to give it? Thanks.
I fully agree with this, but the problem is hsphere sometimes flies through its tasks, and sometimes goes at the pace of a sleeping sloth. Also the data sync is a bit sporadic so ensuring data is there is an important factor, we only have about 12-16 hours notice ourselves on it when it happens.
The redirect was just recently added, but you can’t connect directly like that now you need to put in for server:
173.0.136.201,5212
it needs the comma like that.
You can make a cname/a record for a custom name like ‘mssqlall.bassodesigngroup.com’ then use that and put the ,5212 after it.
All sql servers will be in order like 5204, mssql4, 5205(not up yet) mssql5, etc.
I understand that, but at this moment we don’t even know which servers you plan to migrate first and which later… For me no problem that dates will change, but now there are no target dates at all for upcoming migs. (but instead following @jodohostcom on twitter…)
Regards, Jan-Pieter
Stephen, perhaps link to that post at the top of your migration status page?
BTW, has win33 been migrated? I have 2 clients on win33, which is in the old DC, and they’re using MSSQL12, which is now in the new DC.. is that a problem?
no 33 is going tonight, so be on the lookout for any custom changes done there. Win33 has been a bit weird on us showing ‘FAILED’ on a number of items recreated, but I’ve checked literally dozens (60+) and every ‘fail’ was indeed set fine.
asp on, asp.net enabled, awstats on, etc all had some fails a bit abnormal, but every time the function was actually on.
