I have been playing around with the scripts that you set up in Managing Elastic Scale with Scripts - http://azure.microsoft.com/nb-no/documentation/articles/sql-database-elastic-scale-manage-scripting/. The first time that I run the scripts, everything
works fine. I get the Shard Map Manager Database created as well as today's shard. I then delete those 2 databases through Enterprise manager using the commands
drop database [Shard_20150419]
drop database [ShardMapManagerDb]
When I run the scripts again, the databases are created, but there are no tables inside the databases. The scripts complete without errors and the output from the output window looks the same as the first time I created them. What's going on here? Do I need to do more to delete the databases than just drop them? When I wait another day, I get the same behaviour. The first time it works, then second time, empty databases. I have tried dropping and recreating the jobs in between runs, and that doesn't fix the problem. I have also tried publishing the jobs, and that doesn't fix the problem. I really need to know what is going on here before I can continue evaluating this technology.
Regards,
Paul
- Edited by phebhardt Monday, April 20, 2015 11:58 PM Changed title of article
- Moved by Mekh SubbaMicrosoft contingent staff, Moderator Tuesday, April 21, 2015 8:10 AM Moving to correct forum