I'm working on building out a db2 database from scripts for build verification purposes.
Basically we have a set of db2 scripts that were extracted quite a while ago, and we'd like to build out these scripts into a db2 database, so that we can compare against production and make sure that they match.
Any thoughts on available tools? Or will we need to build this ourself?
thanks!
Sylvia
Update: Ideally this tool would have error trapping, logging, all that kind of stuff. Kind of like the Red Gate tools for SQL Server, but for DB2.
db2 comes with a command line processor.
db2 -tvf <filename>
You need to initialize your db2 environment first.
Related
I am trying to migrate oracle db to posgresql,and I am using unixODBC to make application db agnostic. UnixODBC provides different drivers for oracle and posgresql to achieve DB agnostic. And it is working very fine on C++ & perl libraries.
But in bash/ksh scripts sqlplus is used to run queries on oracle.
Now for unixODBC based db agnostic approach what is the good alternative to sqlplus to use in these scripts?
Please note:
psql from postgresql is not useful as it will defeat the db agnostic purpose
isql utility provided by unixODBC is very simple and lacks many features thus not very effective
PS: This question is specific to bash/ksh scripts.
There is a command isql which can help.
https://www.ibm.com/support/pages/checking-odbc-connectivity-linux
I'm using EF 6 (Code first) with the IBM.Data.DB2.EntityFramwork nuget package to access a db2 database server. Working locally it all works as expected, but when deployed to a test server I get an exception: "System.MissingMethodException: Method not found: 'Void IBM.Data.DB2.InternalStruct6.SetDefault()"
I'm no DB2 wizard but I think the issue is related to a incompatible version of the db2 client drivers installed on the test server (9.7?). Entity framework 6 support needs version > 10.5. (I must have installed the 10.5 version locally at some point).
It would be nice to be able to run the application on any pc without additional dependencies, so my question is: Are there any way of skipping the db2 clients/drivers installation, and rather reference certain db2 dll's (or other nuget packages), to access db2 db servers?
Ok, I think asking the question resulted in a moment of enlightenment.
I guess the answer is NO, as the db2 clients/drivers actually installs the db2 odbc data source driver for db2. (Located in Administrative Tools -> Data Sources (ODBC)).
Has anyone managed to use Postgresql as a datasource for SSAS? The Postgresql .NET connector seems promising, but the SSAS view wizard does not seem to be able to see the tables in the database.
Try using the ODBC connector. I've had success getting other tools to connect to PG using it. The EnterpriseDB installers not only include a well packaged, working version of PG for windows, they include working, correctly installed drivers.
http://www.enterprisedb.com/products-services-training/pgdownload
try pg_bulkload for load from via c# & from mssql to pgsql
copy & bcp (ssis) for second direction (pgsql->ssas)
242
It is actually possible to hack the Postgresql .NET connector and implement a "MSSQL compatibility mode", where the [ and ] around tables and schema names are removed. Using this, the list of tables does not appear in MS SSAS, but it is possible to replace them by views.
I would like to run SSIS 2008 packages on a server that does not have SQL Server 2008 installed on it. I have a simple package to test the concept, but it fails to execute. The return code is 9020 which I have not seen listed as a return code elsewhere.
I have copied the following files to the test server that does not have SQL Server 2008 installed on it:
SelfContainedSample.dtsConfig
Package.dtsx
DTExec.exe
I am attempting to run the package using a batch file. The line in the batch file that runs the package is:
"%dtexecloc%\dtexec.exe" /FILE "%packagefolder%\Package.dtsx" /CONFIGFILE "%configfolder\SelfContainedSample.dtsConfig" /CHECKPOINTING OFF /REPORTING E >>%logfile%
set rc=%errorlevel%
I am wondering if there are other requirements that need to be satified to run an SSIS 2008 package on a server that does not have SQL Server 2008 on it? .NET Runtime? SSIS 2008 runtime?
Please share your advice if you have a solution or have met this issue before.
The following is from a discussion about this topic on
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/134585b4-7960-4b1c-938b-d5421a4d0fdb
SSIS is a server component. To run a
SSIS package you need to license and
install the full SSIS server, there is
no client only. A machine that hosts
SSIS packages must be licensed as a
full SQL Server, a CAL is not
sufficient.
There is no remote execution
functionality built in. The common
workarounds are to use a SQL Agent job
or a development technology such as a
web service or web page to bridge the
gap between the server and client.
The Quote is from Darren Green (about 4 answers down on the discussion). Jamie Thomson gives a similar answer.
You need the SQL Server server-side binaries. SSIS does not have to be running though.
I'm not sure if SSIS has to be installed as a component though, or just the general binaries.
We did some tests recently to work out what is needed for the "lightest" way to run SSIS
KB 942176 refers to the role of the SSIS service
I have to make installer that installs Postgresql before our application, makes database and execute some sql scripts against the database.
Now I'm using the Bootstrapper to install Postgresql and then our application and using Wix install sequence I execute SQL script that takes care of the rest.
I'm wondering if there is any way to do it without Bootstrapper? I've read about Wix SqlExtension but can't figure out if it's database independent or if I can install databese server with it...
The WiX SqlExtension is SqlServer specific. However, it shouldn't be that hard to plumb in a Postgresql layer underneath it. IIRC, the actual database calls are pretty abstracted away.
Also, a bootstrapper isn't the correct place to do static configuration either. If this is really configurable data then maybe an entirely separate app launched at the end of install makes sense. But if it's just creating databases, I'd put that in the MSI itself.