When I try to connect a TSQLConnection with MSSQLConnection it returns dbxmss.dll missing.
There is no such dll in all of my C: drive (I checked also ...\bin\ folder)
I've already uninstalled and reinstalled Delphi (XE4).
And, after that, it is still missing.
The table was created with Microsoft SQL Server 2012 (v11.0.3128.0) Management Studio.
Am I doing something wrong?
It appears you're using a Professional or lower SKU of RAD Studio. The lower editions don't come with drivers for SQL Server or Oracle for DBExpress.
You'll need to switch to using ADO (via the components in the dbGo component palette page), upgrade to a higher SKU (Enterprise or Architect), or find a third-party dbExpress driver to use instead.
Download Zip folder
Extract libmysql.dll, Place it in the folder "C:\Program Files (x86)\Embarcadero\RAD Studio\9.0\bin64
Related
Continuous Build Database Project fails when building on TFS server. We have Visual Studio 2013 Shell (Integrated) installed. There does not appear to be a way to install SQL Server Data Tools 2013 thru' Tools > Extensions and Updates... menu.
The redacted error is below...
C:\TFSBuild\XXX\XXX\Database_CI\Sources\Database\XXX\XXX.sqlproj (126): The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
Has anyone experienced this? Is there a solution or work-around? Is SSDT available for VS 2013 Shell for SQL Server 2014?
I have recently installed the Visual Studio Shell (Isolated) and (Integrated) on our build server and it does not include the SQL Server tooling components. I found out that SQL Server tooling is built in to the following versions of Visual Studio (see here):
Express for Web,
Express for Windows Desktop,
Professional,
Premium, and
Ultimate
I would recommend installing at least the Professional version and then you should get the SQL Server Data Tools components that are required for building.
SQL Server Tooling is now built into the above listed versions of Visual Studio 2013 (SSDT and Visual Studio versions) and the latest March update of Visual Studio 2013 now includes SQL Server 2014 support (SQL Server Data Tools for SQL Server 2014 is available.)
To force your build to use the correct version of MSBuild set the Process - Advanced - MSBuild arguments = "/p:VisualStudioVersion=12.0" (without the quotes) as shown.
You can download SSDT for VS2012 here and that should get the database pre-reqs on your build server.
I do see mention of "Sql Server Tooling in Visual Studio 2013" on this landing page, and I think it implies these tools should be available with the shell, so if you could, check to see if you have that targets file somewhere on your build server.
Go into C:\Program Files(x86)\ and do a "dir Microsoft.Data.Tools.Schema.SqlTasks.targets /s /b" and see if something comes up.
Right now it's hard-coded to this location:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets
You might want to see if the file already exists, but in another location, like in an "v12.0" folder instead of the "v11.0" subfolder.
EDIT
Actually, what's the value on line 126 of your .sqlproj?
If it says this:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" />
Change it to read:
<Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" />
Then have everyone test it using diagnostic logging, then gather the logs and compare them to make sure that version is consistent so you can start phasing out the legacy bits.
I had the same issue and fixed it by downloading and installing the following
dacframework.msi
SQLDOM.MSI
SQLLS.MSI
SQLSysClrTypes.msi
from here:
https://www.microsoft.com/en-au/download/details.aspx?id=42295
I created SSIS will do task like get data from oracle to sql server.i run ssis package run in my local system.it is working fine but i deployed ssis package in remote system and trying access from sql procedure. I'm getting error like below.
Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version on 7.3.3 or later client software installation.
Please let know if any solution there?
Simplest solution: The Oracle client is not installed on the remote server where the SSIS package is being executed.
Slightly less simple solution: The Oracle client is installed on the remote server, but in the wrong bit-count for the SSIS installation. For example, if the 64-bit Oracle client is installed but SSIS is being executed with the 32-bit dtexec executable, SSIS will not be able to find the Oracle client.
The solution in this case would be to install the 32-bit Oracle client side-by-side with the 64-bit client.
Technology used: Windows 7, UFT 32 bit, Data Source ODBC pointing out to 32 bit C:\Windows\System32\odbcad32.exe, Oracle client with both versions installed 32 bit and 64 bit.
What worked for me:
1.Start -> search for Edit the system environment variables
2.System Variables -> Edit Path
3.Place the path for Oracle client 32 bit in front of the path for Oracle Client 64 bit.
Ex:
C:\APP\ORACLE\product\11.2.0\client_32\bin;C:\APP\ORACLE\product\11.2.0\client_64\bin
1.Go to My Computer Properties
2.Then click on Advance setting.
3.Go to Environment variable
4.Set the path to
F:\oracle\product\10.2.0\db_2\perl\5.8.3\lib\MSWin32-x86;F:\oracle\product\10.2.0\db_2\perl\5.8.3\lib;F:\oracle\product\10.2.0\db_2\perl\5.8.3\lib\MSWin32-x86;F:\oracle\product\10.2.0\db_2\perl\site\5.8.3;F:\oracle\product\10.2.0\db_2\perl\site\5.8.3\lib;F:\oracle\product\10.2.0\db_2\sysman\admin\scripts;
change your drive and folder depending on your requirement...
After you install Oracle Client components on the remote server, restart SQL Server Agent from the PC Management Console or directly from Sql Server Management Studio. This will allow the service to load correctly the path to the Oracle components. Otherwise your package will work on design time but fail on run time.
In my case this was because a file named ociw32.dll had been placed in c:\windows\system32. This is however only allowed to exist in c:\oracle\11.2.0.3\bin.
Deleting the file from system32, which had been placed there by an installation of Crystal Reports, fixed this issue
I am facing the problem of finding SQL Server Profiler in SQL Server 2005. Is there are any options to enable it or to reinstall it?
Two possibilities.
First, you're running Sql Server Express. That doesn't come with Profiler. In that case, you can use this tool, which is an open source version that is pretty good. I've used it a few times myself (not associated with the project, spamflaggers).
Else, you need to rerun the installer and add Profiler. If it didn't get installed, it has to be installed. That's the general state of things in the software world.
You can select SQL Server Profiler from the Tools menu in SQL Server Management Studio.
The file is located on my computer under:
"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\PROFILER90.EXE"
If its not there you may have to select the client tools from the SQL Server installer.
Simply navigate to add/remove programs, and click 'change' on the SQL Server 2005.
I had the same problem and it was because I had installed Management Studio Express before I installed the full version. You can't have more than one instance of Management Studio, therefore, it won't install the full version over the express version. I found that I had to remove the express SSMS and then install the full SSMS:-
Go to Control Panel/Programs and Features (in Windows 7)
At "Select an instance", choose "Remove Shared Features Only"
Choose "Management Tools - Basic"
You can then run the installer again and install the FULL SSMS. Dunno if this was the problem you were having, but hopefully someone finds it useful.
Where can I download that? All I can find is the express version. I bought the SQL Server Developer 2008, but the Studio wasnt installed along with it...
Thanks
SSMS is ALWAYS part of any non-express edition including DEV edition (I mean you dont need to download it seperately).
When you install SQL Server Dev. (or any other non-express edition), during setup process you will come across a screen where you can select which components to install (e.g. SSIS, SSRS, SSAS, BIDS, BOL etc). In that step you will need to select SSMS to get it installed.
For some reason if you have skipped that step you can run setup again and just install SSMS only.
But I dont think there is any seperate download available for "normal" SSMS.
This is an annoyance because access to SQL Server from a workstation is necessary and the only way (as previous posters mentioned) is to use the full SQL Server licensed installation package.
You'll run the setup to install as though you're installing the full database. In some cases, setup will detect that you'll need to first install some dependencies. When you come to the Feature Selection, you can select the Management Tools only.
http://i.stack.imgur.com/ochff.gif
You can download eval version from this link -
http://www.microsoft.com/sqlserver/2008/en/us/trial-software.aspx
The express edition are the free versions.
The express version is the free version. If you want another version you need to buy it. My best guess is that it is included in one of those packages on in the microsoft store.
EDIT
According to a forum:
I`m not sure what you mean - you ask
for Management Studio and there is a
download link for SQL Server
Management Studio Express.
Or will you buy a SQL Server Standard,
Enterprise or Datacenter Edition -
then you have the "normal" SQL Server
Management Studio.
I installed SQL 2008 Enterprise edition all work properly during the installation all requirement are passed then after click finish go to :
start --> All Programs --> Microsoft SQL Server 2008 --> only found the Configuration Tools and import export data
any help plz
During installation you need to make sure to install management tools.
I get that occasionally when istalling on a rebuilt machine or server. I have no idea why it happens, but to make sure it doesnt happen, I normally choose the path where I choose the features during install and make sure you have the i think its called client tools or something checked for install. I used to get it all the time until I changed.
If you have different versions installed, it will show only one of them in the Start/Program Files Menu. However you might be able to find the exe file down the road at somewhere like:
"$\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe"
for the 2008 version and
"$\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe"
for the 2005 version.