Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
What is the difference between
project 2010 and project server 2010
specially integration with sharepoint 2010 ?
With Project 2010 Standard you can:
manage local projects
manage shared projects stored on network shares
manage resources stored inside of a project or manage resources stored in a resource pool file
link local and shared projects
if ODBC (database) is used to store project plans - you can build reports from the projects' data
Project 2010 Pro is Project 2010 standard + ability to work with Project Server
With Project Server 2010 you can all you can do with Project 2010 Standard + :
manage resources, security, views, templates, custom fields with lookups from one place
assign workflows to project plans
you get one more interface to your project plans: Project Web application. It costs slightly cheaper than Project: about $150 for PWA and $1500 for Project Pro.
your people can report their timesheets and progress directly to projects
you are getting better reports: Project Server includes BI reporting
API to work with projects which is much better than COM provided by desktop MS Project
Export tasks to SharePoint and Outlook (Exchange Server)
People believe that Project Server is Enterprise solution and it gives them some super enterprise functions they were never had with just desktop MS Project.
Practically you can implement the most of the Project Server features using combination of other technologies, but sometimes it is better to get something already done than reinvent a wheel.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
We have few classic ASP web applications which are to be converted to ASP.NET Core. Few questions:
1) Are there any tools which can help in migration
2) I have Windows server 2016 - what version of Visual studio , edition and framework is required to be installed on the server ?
3) Are there any other software / NuGet packages which are required as pre-requisite ?
4) What should be the approach taken for such migrations ?
Thanks
ASP.NET and ASP.NET Core, despite both having "ASP.NET" in their names are fundamentally different things down to their core, no pun intended. As such, no, there is no "tool" to migrate for you, because it basically requires a rewrite. You should not look at moving to ASP.NET Core as a "migration". You are creating a brand new application. The way you structured your previous app, how you chose to do things, the very architecture itself, will all need to be re-evaluated, just as if you were starting from scratch, because you essentially are.
I'm actually in the middle of such a "migration" myself, but I've taken the opportunity to move to a microservices architecture. As such, I'm essentially just breaking off pieces of the old application and replacing them with microservices. This makes it relatively easy and straight-forward to start using ASP.NET Core while at the same time keeping your existing ASP.NET application working, limiting the scope of the changes required. Eventually, once all the core functionality is spun off, all you'll essentially have left is the UI, which is a rather simple replacement overall.
As far as tooling, you must have Visual Studio 2017, edition does not matter. 2015 can only work with up to .NET Core 1.1, and not well even then. 2019 will be a better option once it's generally available. Basically, just use whatever the latest GA version is always. There's some benefit with the Enterprise edition as you get things like Live Unit Testing with that, but you can develop full ASP.NET Core apps on even the free Community edition, just without all the Visual Studio extra bells and whistles you get for paying for higher versions.
NuGet packages are specific to your app, so you'll decide on those as you build. As far as other software goes, if you want to take the same microservices architecture approach, you'll want to have Docker for Windows installed. Generally, you'll of course also need the .NET Core SDK you plan to target installed, as well.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I have a system that runs on MSAcess and the client want to upgrade this to SQL Server. What version do I need to have on my development machine? If the client has SQL 2010 Enterprise will it be compatible with SQL Express on my development machine? What are the pitfalls of having these two different versions? Will I be able to backup my Express version and restore it to their 2010 Enterprise version?
All help will be greatly appreciated.
Regards
Mac
The best option is a Developer Edition. It has feature parity with Enterpise Edition but, as is only licensed for Developer work and not for production, it costs around $50.
Express Edition is also a feasible choice, as is free, but you'll miss some of the more advanced features and if your client(s) ask for these features you won't be able to test. Examples of useful features you'll miss are SQL Server Agent, Reporting Services, SSIS or Database Mail.
Will I be able to backup my Express version and restore it to their SQL Server 2012 Enterprise Edition?
Yes, as long as you make sure your version is at most the client deployed version and not any newer. You also need to ensure all your application is contained in the database (no dependency on logins, agent jobs etc), which is tricky. But you should absolutely do not do this. Your deliverable cannot be a database binary (mdf/ldf or backup), but it must be a script to deploy the database. If you fail to do this, your will have a big problem after one week when your client will ask for an update. Threat the database as code. See Version Control and your Database. Read about Rails Migrations for a good approach to this problem.
If you develop your application with an Express edition you should not have any problems if the user has a Enterprise edition running.
You can see the feature comparison sheet following this link: Features Supported by the Editions of SQL Server 2008 R2.
P.S. There is no SQL Server 2010. I think you mean SQL Server 2008 R2, thus the link provided links to that content.
If you upgrade your Access Database to a SQL Server Database you might have problems if you use Multiple Values in Access. For further possible incompatibilities follow this link.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am very new to TFS and SharePoint so I hope I can explain myself as best as possible.
We currently run a single server farm that runs on Windows 2007 Standard, SQL 2008, TFS 2010 and SharePoint 3.0. I have been given the fun task of upgrading this to TFS 2012 and SharePoint 2010!
Now I have been following the steps that Microsoft provide but I am still hitting problems along the way and need to know the best possible approach!
I have built a new server with all TFS & SharePoint requirements. Windows 2008 R2, SQL 2008 R2. I have also installed TFS and SharePoint 2010. Before I configure anything I then used TFS backup and restore tools provided with the new installation to back up the existing Database on the old server and restored the databases onto the new server running SQL 2008 R2.
Before backing up the databases I made sure I have a backup of the report server encryption key. When trying to restore this I have the following problem?
Microsoft.ReportingServices.WmiProvider.WMIProviderException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
Have I missed any steps for the upgrade?
Also when performing this upgrade, is there any chance of this interrupting our current TFS & SharePoint production server?
It sounds like you selected "Install but do not configure" when installing Reporting Services. For TFS 2010+ you need to have it configured as the TFS install will not do that for you like it used to in 2005/2008.
I have a blog post that includes how to configure RS: http://nakedalm.com/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/
Although this is for 2013 it applies equally to 2012.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
As the title suggests, can Sharepoint 2010 be installed and successfully run on Azure cloud?
I am aware that Azure used to be stateless and as such could not support Sharepoint, but recent articles and posts seem to suggest that Mirosoft have resolved this.
http://www.theregister.co.uk/2012/06/27/microsoft_windows_azure_cloud_epiphany/
I have checked the Azure website and Sharepoint is mentioned but not specifically 2010 and I want to be sure it's a supported environment with no catches or unforeseen problems.
With the Spring 2012 release (which you read about with your link above), there are now Virtual Machines which are persisted to disks in Windows Azure blobs. SharePoint 2010 is one of the applications that's been specifically tested in this environment.
See this support page, where SharePoint 2010 (and other software) is explicitly called out.
You might find this TechNet article on creating a VM instance in Azure for a SharePoint farm helpful.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I work extensively with MySQL and have no experience with SQL Server. But I have an upcoming project where the existing site's database is on SQL Server. I will be needing to make periodic glances at the existing database, to make SQL dumps most likely so I can write a migration script to the new site database in MySQL. The client will be regularly updating this existing database so just asking for a one-time dump will not help.
Ideally I am looking for a web-based (or desktop based) tool which will allow me to log in to the SQL Server database (I have remote access) and allow me to make a dump or perhaps browse the database structure. Something similar to phpMyAdmin would be nice.
Update: I should clarify that web-based tools which are ASP based are not ideal. As much as I'd like to learn more about ASP, I do not have the time to set up another environment just to run the tool. Something hosted by a 3rd party would do the trick.
Several options are available (probably quite a few more, too):
SQL Web Data Administrator
SQL Server Web Tools
Article on web based admin tools
CiberSQL Web Admin
myLittleAdmin (commercial)
SqlWebArchitect
MSSQL Web Admin (broken link)
DBHawk (commercial)
You can also connect via ODBC to your remote MSSQL server then use MSAccess or OpenOffice to connect, browse or backup.