I have the following installed on my server
Crystal Reports Basic Runtime for Visual Studio 2008
and
Crystal Reports for .Net Framework 2.0 (x86)
I am moving to a new server. The old server is Windows Server 2003. The new Server is Windows Server 2012 R2 Standard (64 bits)
I want to install the same or equivalent software on my new machine so my software will continue to run. I don't think I need any licenses. Please point me to where I can download the installs
Bob
this is a good poin to start
http://scn.sap.com/docs/DOC-7824
the is ll the type of setup, you need the runtime i think.
Related
We have a C# web project authored in Visual Studio 2013 which incorporates a Database Project, and I've set up a number of TeamCity build configurations to do Continuous Integration.
Team City is working well for us at the moment with all of our code checkins going automatically into the integration environment.
SSDT is also working well for us, we are easily able to share and publish database changes within the development team.
What I want to do now is get TeamCity to automatically build the Database Project and deploy it into the integration environment.
We do not have VS2013 on the build server, and would rather not install it there. We are all running SQL Server 2012.
I have read a few questions and articles about "headless" builds of *.sqlproj projects e.g:
How to build .sqlproj projects on a build server?
These approaches seem to be quite manual and fiddly and related to SSDT 2012 - has anyone got a reliable configuration for the versions we're using?
We've got SSDT working on our build server without requiring a copy of Visual Studio. In our case, we did a full install of SSDT because that will give you the necessary components, including the Visual Studio IDE shell. It was also a bit less fiddly than trying to make the admin install point and install just those bits. We added the folder containing sqlpackage to the path and made sure that we could get to the latest MSBuild executable (part of the .NET framework). There's no need to install a full copy of Visual Studio unless you happen to need it for some other reason on that machine.
This article goes into a bit more detail: http://sqlproj.com/index.php/2012/03/headless-msbuild-support-for-ssdt-sqlproj-projects/
Summarizing that article, here's what you need:
Install the Microsoft® SQL Server® 2012 Data-Tier Application Framework
Install the Microsoft® SQL Server® 2012 Transact-SQL ScriptDom
Install the Microsoft® SQL Server® 2012 Transact-SQL Compiler Service
Install the Microsoft® System CLR Types for Microsoft® SQL Server® 2012
Install the SQL Server Data Tools Build Utilities from the Administrative
install point. (this is where we used the full install)
It's been a while, but you might be able to just make sure that machine is connected to the Internet and run the latest SSDT installer to install SSDT and all of the pre-reqs. At that point, you've got the necessary bits to build SQL Projects.
I am preparing to do some web development against a SQL Server 2012 server on a fresh install of win 7 x64 development VM.
What should I install first, visual studio or SSMS?
This is my favorite order:
Windows update before installing anything.
SQL Server 2012
If you have SP1 integrated with you ISO file, skip to step 4.
If you have both SP1 and U5 integrated with your ISO file, skip to step 5
Unselect SQL Server Data Tools during installation (step 8 will install the VS 2012 templates instead of these old 2010 ones)
SQL Server 2012 SP1
SQL Server 2012 SP1 U5
Visual Studio 2012
If you have U3 integrated with you ISO file, skip to step 7.
Unselect SQL Server Data Tools during installation because we'll install the updated bits in step 7
Visual Studio 2012 U3
SQL Server Data Tools - BI (adds BI project templates to Visual Studio 2012)
SQL Server Data Tools (allows you to manage SQL Server 2012 from within visual Studio 2012)
Windows Update
ReSharper
StyleCop
SQL ToolBelt
Neither - you can install them in any order. While you do get the occasional question about it in various different forums, I have done this and never had an issue.
SQL does have a Visual Studio dependency (formerly) called BIDS, but Visual Studio can install over/around this no problem.
Note that this answer is correct when using the initial SQL 2012 release (as that was the latest edition when this question was asked). Subsequent releases may have changed things. I have made this answer CW to encourage others to edit it as necessary to include info about later versions.
I don't know if there is a different way for VMs but on Windows we used to install SQL Server first, as some of the configurations of Visual studio conflict with SQL Server configurations if it was installed before
No direct dependencies found between the two components, installing Visual Studio first then ensure that .NET Framework installed properly is my approach, then installing SQL Server, but in all cases the SQL Server installation installs the following software components - 2008:
NET Framework 3.5
SQL Server Native Client
SQL Server Setup support files
My approach:
Visual Studio 2008.
Visual Studio SP1.
SQL Server 2008.
Run Windows updates.
Useful question here
I have a centralized Microsoft Sharepoint Server and SQL Server on Windows Server 2008 intalled. I am new to sharepoint. In my local machine i have installed Visual Studio 2010 Ultimate Trial version. When i goto create new share point project in the visual studio, I am getting an error message saying,
"A sharepoint server is not installed on this computer. A sharepoint server must be installed to work with sharepoint projects"
Is it possible to develop the sharepoint application like this? if yes. can you please let me know what i can do?
--
Regards
You should install SharePoint 2010 on that machine. Either install it on Windows 7-8 or Windows Server 2008-R2
http://msdn.microsoft.com/en-us/library/ee554869.aspx
Check this Installing Microsoft SharePoint Server 2010 on Windows 7 x64 along this follow msdn.
you should have 64-bit version of Windows 7. then follow the step
mentioned in the above link. Install the additional prerequisites carefully else the installation will cause some error.
I have installed .net framework 2.0 and now I am trying to install Visual Studio 2005 Express Edition from the Internet, but when I execute the setup file I am getting the following error:
"The upgrade patch cannot be installed by the windows Installer service because the program to be upgraded may be missing or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch".
Can anyone tell me what is the error and how should I rectify it?
Please note that I am already having Visual Studio 2008 installed on my system.
Please help me!
Thanks in advance!
It sounds like you are trying to install the Service Pack or an invalid file. When installing Visual Studio 2008 and choosing the default installation mode it will already install SQL Server 2005 Express edition on your machine if it is not already installed.
If you did a custom install you can re-run the Visual Studio 2008 installation and select to install SQL Express.
Also make sure you don't have Sql Server 2008 installed, and if you have do an advanced install on Sql Server 2005 express and change the instance name to something else. I would recommend rather installing Sql Server 2008, either from the internet or from the Sql Server Installation Disc, by choosing Express edition during installation.
I wanted to get some feedback about the problems we might face if we deploy Sharepoint 2007 on Windows 2008 instead on windows 2003
Windows SharePoint Services 3 is supported just fine on Windows 2008. You'll need to make sure that you're using SP1.
See answers on ServerFault:
Installing Office SharePoint 2007 on Windows Server 2008 R2?
Installing Sharepoint 2007 on Windows Server 2008 R2
To save you time two main points of the solution are:
Create your own slip-streamed installation of SharePoint with the latest Service Pack included (SP3 at the moment) and then install this directly onto Windows Server 2008 R2.
Activate .NET Framework 3.5.1 feature in Windows Server to get rid of the Windows Workflow Foundation error