I have data living on the cloud in table storage and I would like to move this down to a development server.
I used to use Clumsy Leaf table explorer but I seem to often have problems where not all the data is moved. It gives an error half way through when I try to import data that I exported from the cloud.
Are there other options for me to move data between one location and another?
By the way I notice this question was asked before but that was in 2011 and the suggested made does not work. Please don't vote to close this as I hope that things changed since 2011.
If you're looking for other tools, may I suggest you look at Cerebrata tools (http://www.cerebrata.com). You could either use Cloud Storage Studio or Azure Management Cmdlets to download data from the cloud and upload in development storage.
Hope this helps
A while ago, I wrote a blog post about the different azure storage and service management tools. Most of the mentioned tools are still valid and they probably improved since I wrote the post. Check it out at http://gshahine.com/blog/archives/2010/11/04/azure-service-management-tools/
Related
I want to know that after exporting solution to azure devops repos can we edit the code or add new features to the solution from repo itself by adding few lines of code and also i am able to see only files in XML format.
Actually in power app while editing we have some visualization of things but how can you do it in repos while developing new features. Please suggest if there is an alternative.
Editing the exported files is currently not supported. You must edit from within the designers in the browser. For powerapps (canvas apps) specifically, there is currently not an offline editing story, but if it does become enabled in the future, you'll see it on the blog at: https://powerapps.microsoft.com/en-us/blog
There are ALM tools for importing, exporting , and working with Azure DevOps. See https://powerapps.microsoft.com/en-us/blog/announcing-general-availability-of-microsoft-power-platform-build-tools/
Update: We've just announced new tooling to support this:
https://github.com/microsoft/PowerApps-Language-Tooling
More here: https://powerapps.microsoft.com/en-us/blog/source-code-files-for-canvas-apps/
I have recently develop an Xamarin forms app which was linked to Microsoft Azure easy tables. This is a B2B app and will only be used by half a dozen users. It has been approved by the App Store. The syncing with the easy tables worked great.
My client is very familiar with Microsoft Access, and wished to be able to view the tables and add/edit data via this software. I successfully set up the express server and using ODBC linked the database to Access. With no problems on that end. I can see the data, delete rows and add/edit data.
But when I checked the app, the sync to the easy tables was hanging. And when I went into Azure. The easy tables are listed but they have no columns or data.
Are the easy tables now defunct because I have used ODBC to access them? Are they now different somehow?
How do I fix this? Is there a different connection I need to use? Do I need to set up a web api now? Do I need to use a different Nuget package/code? I am just not sure which direction I need to head.
The data is still there as I can see it in Microsoft Access.
Or do I just cut my losses and recreate the database and a new set of easy tables? There is not a lot of data to recreate and I have them in CSV files.
If this is the case, what is the best way of my client accessing and adding or editing the data from Azure? I realise the obvious one is developing a mobile app for him. I just wanted to check if there is any other way?
Thanks
Thank you very much for assisting me. Your advice, although did not directly solve the problem. It sent me down a rabbit hole of looking at the data in the actual SQL Database, and when I was there it asked me to login. I remembered I had changed the password to the server, when I was setting up the database in Microsoft Access as I could not not remember the original one (rookie mistake and I should know better). I changed the password back (as I found it in the connection string). Both now work. Thanks again.
I am using Team Foundation Server by Microsoft. I will probably migrate from one account(server) to another account, and I would like to preserve following things:
source control of files
users
scrum sprints (epics, backlogs, tasks, bugs)
builds
Azure subscription:
move all web services
move all sql databases
How can I approach this? Is this manual work one by one, or can I use some tool for migration?
There is a TFS migration tool / body of knowledge that will help you thought most of the items you list under TFS. You can find it here. This should be fairly straight forward unless you have customised process templates which then create a few more headaches. Moving Builds may be tricky, there is a recently released article on scripting builds with YAML which may be of use.
For the Azure components, you can:
Move databases between subscriptions
and I believe you can do similar for WebApps/Services. You can also move subscriptions using PowerShell.
Is Sharepoint my best option to replace an aging network of fileshares? There's approx 1TB of data residing among 3 fileshares (1 DFS, 2 NAS boxes). A document management system is in place for new things - the file shares are now just read-only archives/legacy. Our users would simply need to be able to search for and open the documents.
Users are finding it difficult to locate their documents in the file shares and windows search does not often help. Sharepoint was suggested as something which would play nicely with Office documents (99% of the content) and have a good search facility.
Not being a Sharepoint Developer or having had any training on it, I'm getting a little lost. I have set up a test server to try it out using SP2013. I have managed to index each of my file shares and have created a search page. However, results aren't consistent with the indexted items. I assume I need to somehow get the relevant metadata from the files but I have no idea how to go about this.
Could anyone suggest some resources for help on this subject (my searches have mainly turned up paid-for Sharepoint addons or outdated blogs) and any experience of doing something similar? Also happy for any suggestions on ways to achieve this using other software/platforms.
I went with Microsoft Search Server 2010 in the end.
Sharepoint is basically optimized to be a document manager. I think you don't need to buy or donwload addons.
For your problem, metadata are the key! You need to properly specify the metadata.
I give you the theory of a plan document management in SharePoint 2013 :
https://technet.microsoft.com/en-us/library/cc263266.aspx
A nice introduction to metadata :
http://fr.slideshare.net/gzelfond/document-management-in-sharepoint-without-folders-introduction-to-metadata
Be careful to use the Microsoft documentation for the beginning. From my experience, its difficult to start with this documentation because you have several things in it. There is also good books/ebooks that you can find easily to start well, and probably more simplified than MS documentation.
Does anyone have any strategies/tips/traps for moving to Team System? Should it be done in baby steps, or all at once? Should we migrate our SourceSafe library over, or draw a line in the sand and move forward? Is it worth brining SharePoint into the mix? Any thoughts are appreciated.
I've never had to migrate to TFS, but have used it pretty extensively for the past couple of years.
Regarding your question on Sharepoint, we've found it pretty useful in conjunction with TFS. We use it primarily for documentation management and for storing other "non-technical" artifacts related to the project. Some dev teams advocate keeping documentation in source control alongside source code, which is OK, but in my experience our project stakeholders have an easier time accessing relevent project documentation via the Sharepoint portal than they would having to interface with source control.
I basically was able to distribute the URL to the sharepoint site associated with our TFS team project to the concerned non-technical team members and have been able to avoid constantly e-mailing documents around, so it's been great for us.
It may just be too much work to do it all at once.
I feel that it is easier to divvy out projects to different people one at a time.
That way they can move them across and ensure that each works okay before closing out the SourceSafe.
You will always want a backup of the SourceSafe "database" around just in case.
I do not know how to migrate from SourceSafe to TFS and keep the comments and versions.
By far the easiest it to just add the projects in, but having migrated that way in the past, we always missed the ability to find out what others had done to particular files.
If you find a way to migrate, I would go that way unless it is hideously expensive.