When using Visual Studio with BISM Normalizer (http://bism-normalizer.com/) you can get the below error.
No room is available to display rowsTo fix the error in Visual Studio you need to go to View ➔ Other Windows ➔ BISM Normalizer Warning List.
Below is a T-SQL statement that lets you get information about the IP-address and TCP-port number for a Microsoft SQL-server.
SELECT CONNECTIONPROPERTY('local_net_address') AS IPAddress, CONNECTIONPROPERTY('local_tcp_port') AS PortNumber;
Moving data from DB2 to Microsoft SQL-server (MSSQL) can involve some difficulties, because there has to be a transformation of datatypes from one RDBMS to other.
DB2 and MSSQL doesn’t contain the exact same data types and therefore a translation/conversion between the two RDBMS has to occur.
This article from Microsoft explain how the feature DB2ToSQL handles that conversion. And can also be used for inspiration for your own handling of transferring data between the to RDBMS’s.
The article can be found here: Project Settings (Type Mapping) (DB2ToSQL)
Go to https://www.microsoft.com/en-us/download/details.aspx?id=104113 and download the Microsoft Connector for Oracle V1.2 that fits your OS. Here we’ll be using MicrosoftSSISOracleConnector-15.0.2000.215_x86.msi.
MicrosoftSSISOracleConnector-15.0.2000.215_x86.msi is the 32-bit version of the ODBC-driver.
MicrosoftSSISOracleConnector-15.0.2000.215_amd64.msi is the 64-bit version of the same ODBC-driver.
Install MicrosoftSSISOracleConnector-15.0.2000.215_x86.msi on the machine that needs to connect to Oracle.
When the installation is done you should be able to go to create an ODBC Data Sources with the below new Oracle ODBC driver.
Now you can enter the information needed to get access to Oracle-server through ODBC.
If you don’t have or can’t get access through a TNSNames Connection. Then you can go to another location/server/PC and you TNSPing to get the information needed to use Standard Connection.
NB! It is possible to set e.g. the Initialization String in the Advanced-tab.
The below batch-code (.bat) will ask you for an AD-group. It will then run the command net group for the entered AD-group. Paste the result to a temporary text file and open that text file in Notepad for you to view and search through.
@echo off
set /p gname="Enter groupname: "
net group /domain %gname% > C:\temp\groupoutput.txt
notepad C:\temp\groupoutput.txt
The below batch-code (.bat) will ask you for an AD-user name. It will then run the command net user for the entered user. Paste the result to a temporary text file and open that text file in Notepad for you to view and search through.
NB! It is also possible to use the command gpresult, if the command net user doesn’t work for you.
@echo off
set /p uname="Enter username: "
net user /domain %uname% > C:\temp\useroutput.txt
REM gpresult /user %uname% /R > C:\temp\useroutput.txt
notepad C:\temp\useroutput.txt
Below SAS-code will let you decode BASE64-encoded text directly in SAS.
%let id_all ='<BASE64 ENCODED TEXT>';
%let session_id = %sysfunc(inputc(%scan(&id_all,1,':')===,$base64x80));
%put &=session_id;
SAS uses BASE64-encoding in PROC PWENCODE for SAS001-encoding.
See this blogpost for information about PROC PWENCODE.
Below is a step-by-step guide to install and configure an ODBC-driver for SAS SPD-server. Be aware, that this guide installs the 64-bit version of the ODBC-driver.
If this is to be used by SSIS, then you will need to create these as 32-bit ODBC-connections. SSIS it not able (as of November 2021) to easily handle 64-bit ODBC-connections.
Below example is for the SPDPROD SPD-server library on the SPDSERVER01 server
On the Server-tab
| Name | <SERVER NAME>.<PORT> e.g. SPDSERVER01.5180 |
Press the Configure-button (in the dialog above)
| Server Address | <SERVER NAME> e.g. SPDSERVER01 |
| User Name | <I THINK THIS MUST BE THE USERNAME FOR USED FOR YOUR DBQ> |
| User Password | < THE USER PASWWORD FOR USER USED ABOVE> |
| Connection Options | DBQ='<FOUND IN YOUR SPD-SERVER CONFIGURATION>’ HOST='<SERVER>’ SERV='<PORT>’ E.g. DBQ='<FOUND IN YOUR SPD-SERVER CONFIGURATION>’ HOST=’SPDSERVER01′ SERV=’5180′ |
On the Libraries-tab
| Name | <NAME OF THE LIBNAME ON THE SPD-SERVER TO BE ACCESSED> |
| Hostfile | <NAME OF THE LIBNAME ON THE SPD-SERVER TO BE ACCESSED> |
| Description | <DESCRIPTION> |
| Engine | SPDSENG |
| Options | DBQ='<FOUND IN YOUR SPD-SERVER CONFIGURATION>’ |
If you want to install the 32-bit version of the ODBC-driver after the installation of the 64-bit version of the ODBC-driver.
Then be aware, that the 32-bit version of the ODBC-driver is installed in this folder, if the default installation path is chosen for the 64-bit version of the ODBC-driver: C:\Program Files\SASHome\x86\SASScalablePerformanceDataServer\5.4\lib
If you do not have a tool to test a ODBC-connection available on the machine for the installation. It is possible to test these through PowerShell.
This is possible using the PowerShell code below.
$conn = new-object System.Data.Odbc.OdbcConnection
$conn.connectionstring = "DSN=<NAME OF YOUR ODBC-CONNECTION>; UID=<USERID>; PWD=<USER PASSWORD>"
$conn.open()
$sql = "SELECT * FROM <TABLE IN LIBNAME ON SPD-SERVER>";
$cmd = New-Object System.Data.Odbc.OdbcCommand($sql, $conn);
$rdr = $cmd.ExecuteReader()
$rdr.read()
$rdr.GetValue(0)
$conn.Close();
The below SQL will in a database on a Microsoft SQL-server find all tables with information about the tables schema, name, creation date and modifications date.
select
schema_name(t.schema_id) as schema_name
, t.name as table_name
, t.create_date
, t.modify_date
from sys.tables t
order by table_name
;
The below script in PowerShell can scan a given range of ports for a specific server and will – if a port on the server is open – return the text: TCP port <PORT NUMBER) is open!
foreach ($port in <START PORT>..<END PORT>) {If (($a=Test-NetConnection <SERVER> -Port $port -WarningAction SilentlyContinue).tcpTestSucceeded -eq $true){ "TCP port $port is open!"}}
Example
foreach ($port in 3388..3390) {If (($a=Test-NetConnection MYSERVER -Port $port -WarningAction SilentlyContinue).tcpTestSucceeded -eq $true){ "TCP port $port is open!"}}
TCP port 3389 is open!
If you only want to scan for one port, you can use the following syntax
Test-NetConnection <SERVER> -port <PORT>
or
TNC <SERVER> -port <PORT>