How to setup ODI studio on a Windows server 2012 R2 so that logged in OS users can use ODI Studio 12.2 ?
Do each user have to have their own install of ODI Studio 12.2 in their private directory ?
What privileges are needed for a OS level user on Windows 2012 R2 server to install their own copy of ODI studio 12.2 ?
I usually install it in a root-level directory such as c:\app\oracle\odi and grant the developers read and execute privileges on it.
The user settings are store separately in each user's profile directory %APPDATA%\odi.
Related
I am building a Desktop App with local .mdf database in VB.NET,I am successfully using the software after installing it from the installer in my main machine where I developed the software via Visual Studio(i.e, naturally SQL Server is installed on that machine).
But When I tried to run the same installer in other machine without Microsoft sql server installed -it was installed successfully-BUT it failed while trying to connect to the .mdf database- giving the message as-
What should I do ? Is it only the Microsoft SQL server not insstalled-which is causing problem?
IF THIS IS THE CASE HOW CAN I HANDLE THIS SITUATION WHERE i MAY FIND MY CLIENT MACHINE SQL SERVER NOT INSTALLED?i.e. Should I modify the pre-requisites?(But I don't have the pre-requisite option of MS SQL Server in Installshield LE).
I got it, It was the sqlLocalDB which was needed as I was working with .mdf database files.I installed it from Microsoft site-the SQL Server Express LocalDB addon
I 'v been trying to get user/pwd for a database in a Windows server.
Server is using : Microsoft SQL server management studio - 2017
Microsoft SQL Server Management Studio 14.0.17213.0
Microsoft Analysis Services Client Tools 14.0.1016.232
Microsoft Data Access Components (MDAC) 6.3.9600.17415
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.9600.18861
Microsoft .NET Framework 4.0.30319.42000
Operating System 6.3.9600
You can't get an existing password since only a hash is stored. If you are an administrator on the box, you can reset the sa password as described here and then add accounts and/or reset passwords as needed.
I am trying to silent install SQL Server 2016 components using a configuration file from my installer using inno setup. The OS I am using is Windows Server 2012 R2.
SQL Server Management Studio (SSMS) is available as a separate installer from 2016 version on wards. So I am required to install the SQL Server first followed my SSMS executable through my installer in one shot.
The problem is, the SQL Server is installed correctly but requires a system reboot before installing the SSMS executable. I tried using /SkipRules=RebootRequiredCheck parameter when I execute the Setup.exe and deleting the PendingFileRenameOperations registry entry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager) after the installation of SQL Server. But it still requires a system reboot.
Is there a way to skip the system reboot or any other work around possible for my requirement.
Thanks in Advance.
When trying to install SQL Server 2016 Express in Windows 7 Professional x64 SP1 in VMware I get the following message.
What can I do to solve this?
Here is a workaround for users that need SQL 2016 on a Windows 7 development PC. This will allow the developer to develop and manage them by using using MDFs in LocalDB:
If you don't have Visual Studio 2015 then get it or the 2015 Community Edition
Download and install SQL Server Data Tools. SSDT
Note:
When I initially installed Visual Studio 2015 I chose custom install and selected all options. I was assisting someone else troubleshoot their installation so I installed Visual Studio 2015 Community Edition on another Win 7 Computer. I chose custom Install and under Windows and Web Development options I chose Microsoft SQL Server Data Tools. It stated 2012 SQL Server, but after install and restarting I had both the 2014 and 2016 SqlLocalDB (under 120 and 130 folders respectively). SQL Server Data Tools install may not be needed unless you need SSIS, SSAS or SSRS which I do need.
After all of this you will need SQL Server Management Studio 2016 or higher to connect to the local db and access the 2016 functionality.
After you have installed this there should be a SQL Local DB command Line tool installed. My install location was D:\Programfiles\130\Tools\Binn\SqlLocalDB.exe
The default install location as pointed out by Discosultan may be:
D:\Program Files\Microsoft SQL Server\130\Tools\Binn\SqlLocalDB.exe
My install path was different, but that may be due to the several versions and related components of SQL server that I have installed on the PC and the manner of my installs. Once you have done the install you can search for SqlLocalDB.exe if you have multiple versions and navigate to the 2016 version, (product version 13 in the 130 subfolder).
You can find the install folder path in the registry for SQL 2016 by reviewing the following Registry Entry in HKEY_LOCAL_MACHINE (Abbreviated to HKLM below):
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server Local DB\Installed Versions\13.0
You can run the command line from there or add the directory to the path statement. I have multiple versions so I just go to the directory. Then you create a localDB instance and start it:
SqlLocalDB create "LocalDBExample2016" -s
SqlLocalDB Utility Command Line Reference
From that point if you prefer the GUI you can open SQL server Management Studio 2016 or through Visual Studio and connect to server:
(localdb)\LocalDBExample2016
From there you can add databases, etc.
The mdf and log files will default to C:\Users\[UserName], but they can be moved when creating the databases or copied elsewhere and given to the DBAs, etc. Some of the features won't be available like in memory OLTP tables. Here are the edition comparisons: Editions and Supported Features for SQL Server 2016
As the error message states SQL Server 2016 is not supported in Windows 7. You will have to upgrade to Windows 8 or higher or switch to a Windows Server operating system. Here is a list of all the operating systems (and other hardware and software requirements) in which SQL Server 2016 can be installed.
Late to the party, but while you can't install SQL 2017 Express or 2016 Express on Windows 7, you can install SQL 2014 Express. This may not work for compatibility purposes if you're dealing with a newer version of SQL (although I've been able to install the non-express version of SQL 2016 and 2017 to Windows 7) but if you're supporting something that uses an older version of SQL Express (which, frankly, is likely if you don't have access to a newer OS) this should work well enough.
Short question: I have a visual studio 2015 database project. In my solution. I am using the database first approach for handling my datalayer. How do I open the actual database for management. I can not seem to find any type of SQL server database management tool.
Long question: I am creating a visual studio 15 web application. I am using the visual studio database project for creating and managing the database schema. I was able to create the database during the database compare and update. My server name was "(localdb)\ProjectsV12". I was also able to create my entities from the database. So I know the database exists somewhere. I have never installed anything more than the SQL server express on my local box (I usually use Azure SQL).
According to the error log it is a Microsoft SQL Server 2014 - 12.0.2000.8 (X64) ,Express Edition (64-bit) on Windows NT 6.3 (Build 10240: )
I also have a windows 10 box running Visual Studio 15. So where is the sql management tool?
The localDB is only for development
it can be accessed from server explorer in VS2015 --> Data Connections
connect to server "(localdb)\ProjectsV12" and your DB name
Be aware that you can have multiple SqlLocalDB instances installed on your computer and you can list them by opening up a CMD Window and executing the following command
sqllocaldb versions
For your reference:
The Visual Studio Server Explorer probably gives you all you need, but note you can also connect to localdb from SQL Server Management Studio (download), which is the de facto standard for managing SQL Server databases.