Where does the Access connection string limitation happen?
The meta data for linked tables is stored in system table MySysObjects, where the Connection is a MEMO
field type. That's a 65,536 character field.
Zlatko Matić wrote:
Hello.
Could you, please, help me to optimize my connection string (MS Access 2003,
PostgreSQL 8.1.1. and psqlodbc-08_01_0102)?
' PG_ODBC_PARAMETER ACCESS_PARAMETER
' *********************************************
' READONLY A0
' PROTOCOL A1
' FAKEOIDINDEX A2 'A2 must be 0 unless A3=1
' SHOWOIDCOLUMN A3
' ROWVERSIONING A4
' SHOWSYSTEMTABLES A5
' CONNSETTINGS A6
' FETCH A7
' SOCKET A8
' UNKNOWNSIZES A9 ' range [0-2]
' MAXVARCHARSIZE B0
' MAXLONGVARCHARSIZE B1
' DEBUG B2
' COMMLOG B3
' OPTIMIZER B4 ' note that 1 = _cancel_ generic
optimizer...
' KSQO B5
' USEDECLAREFETCH B6
' TEXTASLONGVARCHAR B7
' UNKNOWNSASLONGVARCHAR B8
' BOOLSASCHAR B9
' PARSE C0
' CANCELASFREESTMT C1
' EXTRASYSTABLEPREFIXES C2
'Connection string
CONNECTIONSTRING:
strConnInfo = "ODBC;Driver=" & Driver & ";Server=" & SERVER & ";Port=" & PORT & ";Database="
& DATABASE & ";"
strConnUserPass = "Uid=" & USERNAME & ";Pwd=" & PASSWORD & ";"
strConnParms = "A0=0;A1=6.4;A2=0;A3=0;A4=1;A5=0;A6=" & A6 & ";A7=100;A8=" & SOCKET &
";A9=1;" & _
"B0=254;B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=0;" & _
"C0=0;C1=0;C2=dd_;"
There are some options I don't understand, for example "Parse statements" and
"Fetch/Declare" and don't know how would it affect performances...
Also, there is a problem with the limited length of connection string that
Access can handle, so I have a problem that I can't input some bigger usernames
and passwords. Therefore I would like to remove some unneccessary parameters,
if possible. Which parameters could be safely removed?
Thanks in advance,
Zlatko
greg.campbell.vcf
Description: Vcard
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|