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?
Related
I have a WPF project and I will use SQL Server database. The instance of SQL Server IT created for me is SQL Server 13 (2016 standard version) on a remove server. When I’m deploying the application on a client’s computers, what version I need to install there as a prerequisite? Can I deploy SQL Server Express 2016 on a client’s computer and access the remove SQL Server Standard edition? I am looking for a simple solution and for a lighter version I need to install on the user’s computers. I cannot install a full SQL Server on each user.
I have searched the net and a similar question has been asked many times, but I didn’t find a clear answer before. Many people started their SQL Server experience using local type databases, like SQL Server CE or LocalDB. In this case specific DLLs and redistributables must be added with the installation program. It is hard to understand at the beginning, but when an instance of SQL Server is on a remote server, this is a different story. Everything is happening on this remote server. There is no need of any SQL Server instances on a client’s machine. Just a connection string must be added. The adapter or Entity Framework will take care of everything else.
We have an application called IpSwitch Whatsup and it's installed in a machine that I can connect to remotely as administrator. This is all in our intranet.
We need to connect to the sql server database being used by IpSwitch Whatsup, but this particular machine doesn't have sql server installed. On the other hand, in sql server configuration manager there is indeed a sql server installation for whatsup (the entry says SQL Server (WHATSUP)).
So, two questions:
How does one go about in connecting to this database? I'm pretty sure I know the name of the database and I already know the server name and instance, so I would like to connect to this DB from a sql server installation in another machine.
How does one configure a sql server installation to receive remote connections if it doesn't have sql server installed?
Thanks.
For the first question, you just type in (or browse) the appropriate instance name and authentication options using SSMS - which is the GUI tool used to manage sql server instances. Note - the term "sql server installation" can mean different things so it is not a useful reference.
As for the second question, review the information here. Note that any task you do in SSMS can be done via tsql - you can see the appropriate commands using the script button in the SSMS dialog windows.
And you can also (and probably should based on these questions) install SSMS on the same machine as your server instance so you can do "anything" "anywhere". Now would probably be a good time to review your disaster recovery options (and start backing up your databases regularly).
I got a task to define various SharePoint farm topologies.
But I haven't any experience about SharePoint and anything else like that.
I found some information about the system requirement and the supported topologies, but I´m not sure if they are really supported.
It's hard to find helpful information. So my question.
I define a three tier topologie.
SharePoint 2016 Server
MSSQL 2016 Server
Workflow Manager Server
Is it supported to share the Database Server with the SharePoint and the Workflow Manager Server?
You can use the same SQL server for the workflow and SharePoint databases without a problem.
In fact I have a site that runs workflow manger from the SQL Server, database and IIS. This was due to the fact the all servers in the farm were Server 2016 and workflow manger is not supported on Server 2016. The only server available to install workflow manager was the SQL server which was Server 2012 R2.
Unless you have an insane amount of workflows, I wouldn't both with a dedicated workflow server, I would split the SharePoint server out into a Web and App Server.
NO, Based on Microsoft best practices SQL server should has its own box, SP and WFM should not be located on the same server to reduce any possible dependency in the future.
ex. sometimes, you will need to renew the certs which are expired. to do so, you need to change the time back.
if SQL and SP sharing the same box, the sites and db transactions will be infected.
another example: if WFM caused any memory leak or throttling, then the SP and SQL will also be infected.
you should dedicate a box for each platform.
1 more thing, the WFM should has odd number of servers. as the Windows/ service fabric uses voting to decide which server to handle the traffic. odd number of servers will allow one of the servers to be identified as preferred server to do so.
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.
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