We have developed a SSIS solution on SQL Server 2008 R2 EE (64 bit) and now a client would like it on SQL Server 2008 R2 (64 bit), are there any issues? Workarounds ?
View Complete Post
We current use SQL 2005 Enterprise Edition and we have our SSIS package working great where the server names are picked from Environment Variables file stored on the server. We are now planning to use SQL 2008 R2 STANDARD edition and for some reason the
SSIS package which works great on SQL 2005 using variables is not working on SQL 2008 R2. It complains about not able to find the location/environment variables.
Question: Is the Environment variables thing supported in SQL 2008 R2 STANDARD Edition?
My current version of SQL server is Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
I want to upgrade this to Enterprise edition. I would like to know the below information please
Any help and guidance is truly appericiated. Thanks.
I will need your advice on a SSIS package which moves IBM DB2 (for z/OS V7) data to Oracle (AIX 10g). Thank you in advance.
Basically, this is a very simple SSIS package (created by SSIS import / export wizard) and just maps column by column. I used IBM OLEDB provider for DB2 to connect the source and Oracle Provider for OLEDB to connect to the destination.
The problem I ran into was that if the DB2 source value contains special (or invisible) characters then this value will be converted to a SPACE (' ') value on Oracle. To be more detailed, take the following example:
On DB2, value 000002D0000002D7 (EBCDIC HEX codes). This is actually a value of a column defined on DB2 as CHAR(8). Please note HEX '00' in EBCDIC stands for NULL and HEX 'D0' stands for character 'K';
On Oracle, this value will be stored as a SPACE (or a string of SPACEs) after data move.
On both DB2 and Oracle this column was defined as CHAR(8).
I guessed this was related to a code page issue, so I tried a few different code page to set for the source property (by setting the DefaultCodePage of the DataFlow source property), I used code page 37, 500, etc... All resulted in the same Oracle value.
The character set on DB2 is EBCDIC and the one on Oracle is ALT32UTF8. I guess it was the source provid
We moved our databases to new hardware today (using copy database wizard)
The new hardware should be better than the old one.
We went from 28 GB ram to 128 GB.
We went from 16 cores to 32 cores (with even more cache etc.). We also moved from external SAN with 40 disks to intern disks (8
Samsung SS805 100gb ssd slc)
According to our own metrics we could get twice the IO using IO m
We are a Prtner and get both of theseas part of our Action Pack subscription. I am also installing CRM 4.0 on our SBS STANDARD 2008 Server. Is it possible to put both the SQL 2008 ENTERRISE R2 and SBS 2008 STANDARD on the same box? CRM
4.0 REQUIRES SQL for the Reporting functions etc.
I need to do this asap as our Old Server is failing daily
Anyone writing data to DB2 on an AS400 with SSIS?
I cannot get the OLEDB destination configured correctly.ÃÂ I can set the destination up with a SELECT sql query, and preview the resultset.
We're implementing SQLServer 2005 peer to peer replication on two servers running SQLServer 2005 EE. We also want each server to use a remote distributor (2 additional servers). Can we run SQLServer 2005 Standard Edition on the remote distributors, or is
it necessary that they too need Enterprise edition?
Functionally, WSS 3.0 sites will work similarly on both Windows 2003 Server - Standard and Enterprise Editions. What would be the reasons for choosing one over the other?
Currently we are upgrading our SQL Server 2000 box to 2008 R2 Enterprise. However, one of the apps locks itself to the Standard edition and will not install to Enterprise (without an additional 100K). With SQL Server Enterprise you can install
multiple instances of SQL Server without additional licensing--my question is, can one of the instances be a downgraded Standard version installation from the SQL Server Enterprise license, or do we have to get an additional SQL Server Standard license for
the same box?
All licenses we are looking at moving to are SQL 2008 R2 processor licenses.