I'm currently using Postgresql Database 9.1 (running Adempiere)
I've been using SQL Server Data Tools on my computer and connecting directly to the server computer to create reports.
Now i want to install the Reporting Services aspect on the computer server so that other users can access the reports through the Report Manager. And also so that it can automatically deliver reports to the users
Is it possible to install SQL Server 2008 in the same computer as Postgresql? And if so, what are the steps that i need to take?
Thanks!
Yes, this is possible to install.
and You should not run into any problems, both servers run on different ports (by default) so both should run happily side by side.
But I dont think its supported, so you won't find any instructions.
Hope it helps.
Related
I have been supporting a product written in VB6 with an Access database for a long time. In many of the installations a mapped drive was used to allow multiple workstations to run simultaneously. Since it seems Microsoft has broken that recently, I need to re-write everything with a new set of tools.
I plan to use VB.net and I would like to use a SQL database this time for the stability. The problem is that the market I sell to cannot / will not support installing full blown SQL Server and all the complexities of managing it.
What I am not able to find any current info about is whether or not SQL Server Compact still exists, whether or not it can be added to a NON web based project and if it will be easy to deploy and be easy to manage like an Access database was.
When I try to follow the directions to add SQL Server Compact to my project, it isn't available in the Data Source drop down list (there are "Simple by ErikEJ" versions listed but they don't seem to work) I have seen SQL Server Compact talked about with regards to web projects but I am building a locally installed .exe. I can't find ANY current info about what flavors of SQL are available right now to add to a local program running over a peer to peer network.
SQL Server Compact is no longer supported and developed by Microsoft, I suggest that you use SQL Server Express, it allows remote connections (if configured to allow it) and has modest resource requirements. Supports a database up to 10 GB of size.
As suggested, SQL Server CE can still be used but is no longer supported. For file-based databases, Microsoft currently recommend SQLite.
For a multi-user system, SQL Server Express is probably your best bet. It's still server-based though, so the server needs to be installed somewhere. For local databases, you can install on the same machine as the application and attach a data file on demand. For multiple clients, you'll need the server installed on a machine accessible to all and a permanently-attached database.
I'm currently working on an application that runs a small SQLite DB, but I want to use .RDLC for reporting.
I generate the reports over my view models, the idea was for them to be decoupled from the DB, but now I run into this snag that I have to install SQL Server in order to use the reporting framework.
I wouldn't want to require my clients to install SQL Server on their machines just to be able to generate reports. They won't be happy about that. And I don't want to redesign my reporting component either(I have something from a previous project which used SQL Server and that works very well. I want to reuse it)
Is there a way to deploy the Reporting framework on the target machine without SQL Server?
Ideally I would like to just just copy the needed libraries in my application's installation folder, under OTS, but I don't really know which libraries to copy and what I can leave out or even if it's going to work this way.
Any insight would be helpful.
No. SSRS will only work on a machine with SQL Server installed on it.
Same with SSAS and SSIS.
So what we ended up doing is installing two nuget packages.
Microsoft.ReportViewer.Windows and Microsoft.SqlServer.Types
This will allow us to use the reporting framework without deploying SQL server on our target machines.
My company has a database located on a server. On that same server there is an installation of SQL Server. I plan on installing SQL Server on my workstation (we have the appropriate license) so I can access the data for reporting purposes. I will need access to SSRS and SSIS on my workstation to help with this process. Will this be issue for me? Will I be able to install SSRS and SSIS or will it only be accessible on the Server's installation of SQL Server?
You can install SSRS and SSIS in your workstation and use the database in your company server as datasource.
Keep in mind your workstation must have access to your company network and your Windows credentials / Sql Server login should have the right permission level in order to connect to the SQL SERVER instance.
I assume you want to install SSIS to design some kind of ETL or data integration process. I'd recommend you only use your workstation to design/develop/test SSIS packages then deploy those packages to your server and run them from it.
The same recommendation if you want to use your workstation as a report server. If you need to delivery reporting services to a large number of users it is possible your machine cannot handle it.
Let me know if this helps.
My company has a database located on a server. On that same server there is an installation of SQL Server. I plan on installing SQL Server on my workstation (we have the appropriate license) so I can access the data for reporting purposes.
No need to install SQL Server Database Server on your workstation to access the data for reporting. You just need to install SSRS and SSIS locally on your workstation if you plan to work on reports and create your ETL packages locally.
I will need access to SSRS and SSIS on my workstation to help with this process. Will this be issue for me?
If you are using a local account to run SSIS/SSRS on your workstation you may run into some permission issues, especially for windows pass-through authentication when accessing data sources - unless you plan to store static data source credentials. You could run the SSRS/SSIS as domain service accounts that have "Write Public Information" permissions to enable Kerberos Authentication, which eliminate the double-hop issues you may potentially face
As pointed out by alejandro you will also need to make sure these service accounts have appropriate permissions set on the remote SQL Server Database Instance
Will I be able to install SSRS and SSIS or will it only be accessible on the Server's installation of SQL Server?
You should be able to install SSRS/SSIS on your workstation, and it doesnt have to be installed on SQL Server
Thanks again for your help. I have the necessary permission to the database and have already started building some queries via SQL Express.
The IT department is going to add a developer server with an installation of SQL Server. We will test the packages on this server and once we are satisfied with the results we will deploy them to the server that houses the databases. I'm assuming they will add the necessary permissions to do so, but we will see. I also installed SQL Express on my workstation and can at least test the TSQL queries on my workstation, and I believe SSRS, before hand.
As a side question:
If there are multiple installations of SQL Server on different workstations/servers, will the server that houses the database have master administrative rights versus the other installations. I ask because each time I install SQL Server I add the admin account, and to me it seems that each installation could have administrative rights. Is that right?
I´m deploying my database to a SQL Server 2008 R2 Express instance that my software also installs. Everything works fine, but on certain target machines there are other instances of SQL Server 2008, 2005, 2000...I know that, theoretically, SQL Server instances may coexist side-by-side. But I also know that there are several conflicts between them. Internet is full of them.
My most common symptom is: server protocols are not installed with a previous installed SQL Server 2008 instance (from other vendor). In SQL Server Configuration Manager, under "SQL Server Network Configuration", the item "Protocols for 'MyInstance'" is just missing. So any client machine can connect to server.
I´d like to minimize the visits to clients house and make my application as self-deployable as possible. Is there something I can do to avoid or resolve instances conflicts? Any advice? Am I wishing for something impossible?
You probably will want to read up on what versions can live on the same server/client:
Working With Multiple Versions and Instances of SQL Server
Work with Multiple Versions and Instances of SQL Server
Both of these links have the chart regarding what side-by-side installs are supported, the second though also includes a little bit more regarding the components and those that will be upgraded to the highest release installed.
With the issue you spoke of with SSCM this can be caused by many things, most of them revolve around a corrupted installation of the management tools; or I mostly see issues with WMI calls on the client. Since most of those settings are available within the registry I would suggest looking at that side to get your instance configured and locked down.
You might also look at SQL Server Compact Edition. It is developed as an embeded database that does not require install of the full SQL Server managemnet tools. You have the same API and controlls that come with full version of SQL Server, just a "compact" install. I have interacted with one application that used it but have not done any development with it.
I have Informatica 9 and an Oracle database in my system. Now I want to install a SQL Server database in my system and add this database to Informatica.
Is that possible ?
Purpose: I need to migrate some of the tables from SQL Server to Oracle database using informatica.
Could anyone let me know, after installing SQL Server, how can I add this SQL Server database to informatica for creating mapping?
Thanks
Sreedhar
Installing the SQL server software on your system and getting informatica to talk to that are entirely different things.
You can for sure install SQL server on your Informatica server system, till the time you are dealing with some varient of Windows. Informatica can be installed on *nix flavours but not SQL server. If your informatica server is not on windows varients, you need to have a separate windows box for sql server installation.
Getting informatica to talk to sql server is going to be dependent upon the platform keys that you have for Informatica. Having the driver and everything is fine, but finally informatica allows interaction to OS/databases based on the platform keys, these keys are normally purchased and have therefore price attached to every additional environemnt/database you want to access.
hth