I need to create a setup package that will not install SQL Server 2008 R2, a sample database, data and .Net 3.5 SP1 along with a setup installation.
I am using Visual Studio 2008. How do i do this?
Is it possible to install the full version, not express from setup package?
You can add other installers to setup packages; however it isn't normally customary to include one for SQL Server for the following reasons:
1, What if they have a different version installed (i.e. you are installing SQL Standard and they already have SQL Enterprise available)?
2, What if they have a SQL server installed on another server that they wish to use?
3, In a couple of years time Microsoft release the next version of SQL server and your software is still installing SQL Server 2008?
For the sample database and data just add the SQL in as a resource and get the app to run the script on first execution.
Related
Client :
- Windows 7 SP1 32bit
- With SQL Express - Advance series installed (with VS2008)
Server:
- Database: SQL Server 2008R2 Enterprise Ed., 64bit
- OS: Windows Server 2008
I always get the message "To design IS packages in BIDS, BIDS has to be installed"
What am I missing here?
Really need your help guys, first time using VS much more the BIDS.
Thanks,
Elmer
You need to install BIDS on your client machine. BIDS is not included as part of Visual Studio, it is part of SQL Server (but runs in the Visual Studio shell). So get your SQL 2008R2 media and run the installation a new instance or add features. You don't need any of the Instance Features, but you should include the following Shared Features:
Business Intelligence Development Studio
Client tools Connectivity
Client tools SDK
Management Tools - Complete
SQL Client Connectivty SDK
I have a server running SQL Server 2008 R2, and the Analysis and Integration services are running on that server.
I have on my Windows XP PC Visual Studio 2008 and SQL Server 2008 R2 Management Studio.
In Visual Studio, when I go to open a new Analysis Services project, it lets me. However, if I try to open a new Integration Services project it doesn't let me and at the end it tells me that:
To install Integration Services, run SQL Server Setup and select
Integration Services.
So I locate the install media and run Setup and chose this option:
New installation or add features to an existing installation.
However, through the steps, it looks as if it's going to install the server engine on my PC, so I hesitated and stopped the process.
I looked around and found this one How to install SQL Server Management Studio 2008 component only that refers to being able to
install just the Client/Workstation Components
but I didn't see that so far.
I also found this: http://www.codefrenzy.net/2011/06/03/how-to-install-sql-server-2008-management-studio/ and she says to
Run the SQL Server Management Studio installer
What is she referring to? I don't see that in my media.
I wonder, wouldn't it be logical to start the install process with asking Client components or Server components or both?
please uninstall and reinstall SQL Server Management Studio(Client/Workstation Components) on client PC, in order to work with SSIS.
I have an application written in MS ACCESS 2007 using VBA, connecting to an SQL Server at the back end. Both Access and SQL Server are running locally.
My machine runs Access 2010 and MS SQL Server Express 2008 R2 (both 32-bit, on WinXP) with no problem.
I have another machine, Win7 64-bit, running both Access 2010 and SQL Server 2008 (NOT R2) 64-bit.
When I run the Access application on the 64-bit machine, I have a drop down box to select the SQL Server which holds the various databases. When I select the server, after a few seconds I get an error:
Run-time error '-2147024703 (800700c1)':
Automation error %1 is not a valid Win32 application.
When I select the Debug option, the yellow arrow points to:
Set oServer = New SQLDMO.SQLServer
The next line is:
oServer.Connect ServerName, strSQLUser, strSQLPwd
In the watch list, I can see that ServerName, strSQLUser, and strSQLPwd hold the right values to access the SQL Server. I've tested these in sqlcmd and successfully was able to query tables.
Can anyone please help me out on this one? I'm not sure what to do next.
Seems like you've got registered a 32-bit SQLDMO on your system that is being used for connection to the 64-bit instance. Check your registry / file system for SQLDMO.dll versions and register the correct one.
Also check MSDN "Installing SQL-DMO" because SQLDMO was scheduled for remove after SQL Server 2008 R2:
Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
SQL Server Database Management Objects (SQL-DMO) has been removed from SQL Server 2008 R2 Express and the SQL Server 2008 R2 Feature Pack. SQL-DMO also does not support Database Engine features introduced after SQL Server 2000. We recommend that you modify applications that currently use this feature as soon as possible. If you must support SQL-DMO, install the Backward Compatibility Components from the SQL Server 2008 Feature Pack from the Microsoft Download Center. Do not use SQL-DMO in new development work; use SQL Server Management Objects (SMO) instead. You can obtain the SMO documentation by installing SQL Server 2008 R2 Books Online.
Thanks for this.
I looked to find SQLDMO.DLL 64-bit version, but although using the Backwards Comparability package for x64, installing using the MSI did not do the job.
I had to manually extract the files and place the correct version (which is ~2MB larger than the x86 version as an indication to knowing which one is the x64) and then run 'regsvr32 sqldmo.dll ' in the command line (very important: need to run cmd as Administrator for this to succeed).
After the module has been registered, my Access front end run great.
So I have made a set up file and install it to target computer which has no .Net 4.0 or SQL Server 2008.
I add them as prerequisites and setup downloaded from the internet the .Net 4.0 and SQL Server 2008.
The setup finished successfully.
When I run the program, it gives an exception:
cannot open xxxxxx.mdf file. it is version 650. and your is xxx...
I searched it out and learned that SQL Server installed on target computer is lower than the database file I created (the database file was created in SQL Server 2008 R2).
So, no connections can be opened.
To solve this, What can I do?
Thank you...
You can't attach a 2008 R2 database to a 2008 instance - you can only go forward, not backward. So either install 2008 R2 at the destination, or you'll have to re-create your database in 2008. If you install 2008 locally alongside 2008 R2, you can create an empty database in 2008 and use tools like Red-Gate's SQL Compare / SQL Data Compare, or the schema compare feature in SQL Server Data Tools, to translate your database relatively quickly.
There is no way to open an MDF file with a lower version of SQLServer.
Of course you could add as a prerequisite SQLServer 2008 R2 (express or full).
But the best course is to distribute a SQL Script containing schema and data.
This could be done using SqlServer Management Studio,
Right click on the database
Select Task
Select Generate Script.
Follow the Wizard.
In the last page of the wizard you could find the button Advanced
Clicking on it will give you full control on what to put inside the script.
The script could be distributed with your application with instructions on how to execute on the target machine.
Originally I had two instances of SQL Server Express 2008 installed on my machine, IT then removed these so that they could upgrade me to SQL Server Management 2008 (with the aim that I would have profiler). My two original instances are there, however under tools there is no profiler. Should the IT guy installed a third instance so that I would have profiler? Or done something different.
The first thing to ensure is that you don't have a whole new SQL Server path under your All Programs folder. I don't recall if SQL Server Express and SQL Server create separate paths in All Programs. Also, look for Profiler under the Performance Tools folder in your SQL Server programs folder.
Check to see if you have the executable on your computer. By default, the Profiler executable is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn. It's called PROFILER.EXE.
Finally, if you still can't find Profiler, run the installer again and do a custom install. Make sure the tools are included for install, which is not the default install normally.