Duplicate Server Name When Creating ODBC

When creating a SQL Server ODBC connection via Data Source applet on a WXP
workstation, when clicking the drop down menu to select the server, two
instances of the same server appear. We recently migrated our SQL server to
new hardware. Turned off the old server and gave the new server the same name
and IP. Also renamed the instance of SQL on the server to the old name. I am
sure this is the cause but not sure how to remove the duplicate entry on the
workstation. We are only seeing this on one workstation? Thanks for your
feedback.
netwerktek
On this computer do the following:
Go to Start - Run
Type in cliconfg and click OK
This will start the Client Network Utility
Go to the Alias tab
There should be an alias defined for this server
Delete the alias. this the where the second entry is coming from.
(Before deleting note the properties. You may need to add it back if
connections fail after deleting it.)
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||That did it. Thank you very much!
"Rand Boyd [MSFT]" wrote:

> On this computer do the following:
> Go to Start - Run
> Type in cliconfg and click OK
> This will start the Client Network Utility
> Go to the Alias tab
> There should be an alias defined for this server
> Delete the alias. this the where the second entry is coming from.
> (Before deleting note the properties. You may need to add it back if
> connections fail after deleting it.)
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Duplicate Server Name When Creating ODBC

When creating a SQL Server ODBC connection via Data Source applet on a WXP
workstation, when clicking the drop down menu to select the server, two
instances of the same server appear. We recently migrated our SQL server to
new hardware. Turned off the old server and gave the new server the same nam
e
and IP. Also renamed the instance of SQL on the server to the old name. I am
sure this is the cause but not sure how to remove the duplicate entry on the
workstation. We are only seeing this on one workstation? Thanks for your
feedback.
--
netwerktekOn this computer do the following:
Go to Start - Run
Type in cliconfg and click OK
This will start the Client Network Utility
Go to the Alias tab
There should be an alias defined for this server
Delete the alias. this the where the second entry is coming from.
(Before deleting note the properties. You may need to add it back if
connections fail after deleting it.)
Rand
This posting is provided "as is" with no warranties and confers no rights.|||That did it. Thank you very much!
"Rand Boyd [MSFT]" wrote:

> On this computer do the following:
> Go to Start - Run
> Type in cliconfg and click OK
> This will start the Client Network Utility
> Go to the Alias tab
> There should be an alias defined for this server
> Delete the alias. this the where the second entry is coming from.
> (Before deleting note the properties. You may need to add it back if
> connections fail after deleting it.)
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Dubious SQL Login?

I want to centralize server logs. All these server services (IIS, ISA, etc)
all know how to log to ODBC, and I want to exploit this so that I have a
central place to analyze logs instead of trapsing through the file system
looking for all these silly log files.
So I made a ServerLogs database, and I plan to have a flat table for each
log. There are of course no relationships here, just a set of flat tables.
These servers that will log through ODBC will need to be able to connect to
SQL Server so I have to make some logins. I would prefer to use Windows
Only authentication because that forces any connection to be authenticated
by Active Directory. But if I do this, then I would have to make Logins in
SQL Server for "Local System" and "Network Service".
Now these logins would only have access to the ServerLogs database, and in
there, would only have "public" permissions. No permissions other than that
which is required to log their log records.
My question is, in this scenario, does it sound like a bad idea to give
LocalSystem and NetworkService access to SQL Server? I just want a reality
check before I do something that might be dangerous or stupid.
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSenseiThe service startup account implicates sqlserver's ability to access
resources. Thus, if you do not want sqlserver to access any resources
outside of the box it's running on, you would use localsystem. If it needs
to access network resources, networkservice is obviously the choice.
Now, as far as users' permissions, you would just need to grant the domain
user (or group) to sqlserver and any desired databased.
e.g.
exec sp_grantlogin 'domain\user' --'domain\group'
go
use db
go
exec sp_grantdbaccess 'domain\user' --'domain\group'
-oj
"Mike Labosh" <mlabosh_at_hotmail_dot_com> wrote in message
news:Ox6%23epiOGHA.3896@.TK2MSFTNGP15.phx.gbl...
>I want to centralize server logs. All these server services (IIS, ISA,
>etc)
> all know how to log to ODBC, and I want to exploit this so that I have a
> central place to analyze logs instead of trapsing through the file system
> looking for all these silly log files.
> So I made a ServerLogs database, and I plan to have a flat table for each
> log. There are of course no relationships here, just a set of flat
> tables.
> These servers that will log through ODBC will need to be able to connect
> to
> SQL Server so I have to make some logins. I would prefer to use Windows
> Only authentication because that forces any connection to be authenticated
> by Active Directory. But if I do this, then I would have to make Logins
> in
> SQL Server for "Local System" and "Network Service".
> Now these logins would only have access to the ServerLogs database, and in
> there, would only have "public" permissions. No permissions other than
> that
> which is required to log their log records.
> My question is, in this scenario, does it sound like a bad idea to give
> LocalSystem and NetworkService access to SQL Server? I just want a
> reality
> check before I do something that might be dangerous or stupid.
> --
>
> Peace & happy computing,
> Mike Labosh, MCSD MCT
> Owner, vbSensei.Com
> "Escriba coda ergo sum." -- vbSensei
>|||> The service startup account implicates sqlserver's ability to access
> resources. Thus, if you do not want sqlserver to access any resources
> outside of the box it's running on, you would use localsystem. If it needs
> to access network resources, networkservice is obviously the choice.
Perhaps you misunderstood, or I misstated:
I want these servers: HTTP, FTP, NNTP, SMTP, POP3, ISA
to be able to connect to SQL Server to write their logs into SQL Server
tables.
The IIS and ISA related services that want to do ODBC logging to SQL Server
all run as LocalSystem or NetworkService. Using Windows Only authentication
in SQL Server, I would have to create SQL Server logins for LocalSystem and
NetworkService so that these other services can ODBC their log entries to
SQL.
My question is whether it's a bad idea to allow LocalSystem and
NetworkService to have logins at SQL Server on behalf of these other
servers, because I know these two important accounts are used for a
MULTITUDE of other things.
In other words, I want to do this:
EXEC sp_GrantLogin 'Local System'
EXEC sp_GrantLogin 'NT AUTHORITY\NetworkService'
GO
CREATE DATABASE ServerLogs
GO
USE ServerLogs
GO
EXEC sp_GrantDBAccess 'Local System'
EXEC sp_GrantDBAccess 'NT AUTHORITY\NetworkService'
GO
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei|||Ah, I see.
Granting any NT acct will only give it a public role. Thus, there is really
no harm. Though, in this case, these system accts are used in many services.
So, granting them access will also allow all others from accessing.
But then again, localsystem already has *full* access to the local
machine...
-oj
"Mike Labosh" <mlabosh_at_hotmail_dot_com> wrote in message
news:Ot91RFjOGHA.2604@.TK2MSFTNGP09.phx.gbl...
> Perhaps you misunderstood, or I misstated:
> I want these servers: HTTP, FTP, NNTP, SMTP, POP3, ISA
> to be able to connect to SQL Server to write their logs into SQL Server
> tables.
> The IIS and ISA related services that want to do ODBC logging to SQL
> Server
> all run as LocalSystem or NetworkService. Using Windows Only
> authentication
> in SQL Server, I would have to create SQL Server logins for LocalSystem
> and
> NetworkService so that these other services can ODBC their log entries to
> SQL.
> My question is whether it's a bad idea to allow LocalSystem and
> NetworkService to have logins at SQL Server on behalf of these other
> servers, because I know these two important accounts are used for a
> MULTITUDE of other things.
> In other words, I want to do this:
> EXEC sp_GrantLogin 'Local System'
> EXEC sp_GrantLogin 'NT AUTHORITY\NetworkService'
> GO
> CREATE DATABASE ServerLogs
> GO
> USE ServerLogs
> GO
> EXEC sp_GrantDBAccess 'Local System'
> EXEC sp_GrantDBAccess 'NT AUTHORITY\NetworkService'
> GO
> --
>
> Peace & happy computing,
> Mike Labosh, MCSD MCT
> Owner, vbSensei.Com
> "Escriba coda ergo sum." -- vbSensei
>|||> Granting any NT acct will only give it a public role. Thus, there is
really
> no harm. Though, in this case, these system accts are used in many
services.
> So, granting them access will also allow all others from accessing.
Agreed. And the only thing SQL Server will let them have permissions for is
"public" access to Just the ServerLogs database

> But then again, localsystem already has *full* access to the local
> machine...
Ha. Yes, I forgot about that. I was just trying to get a reality check
before I accidentally unzipped my fly on the public internet or something
like that.
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei|||>
> My question is, in this scenario, does it sound like a bad idea to give
> LocalSystem and NetworkService access to SQL Server? I just want a
> reality
> check before I do something that might be dangerous or stupid.
>
There's nothing wrong with giving software access to SQL Server, just make
sure that the security is set so that it can't do anything that it
shouldn't. You'll also need to make sure that it's not possible to inject
stuff that you shouldn't be able to.
As a different idea, maybe you should take a look at the SSIS (SQL Server
Integration Services) This is the all new DTS replacement. Using SSIS, you
can pull the information direct from the file system, perform some
transformation and insert the files into SQL. It can be setup on a schedule
so the entire process can be automated, and executed by SQL Server! No need
to give IIS and all those other nasties access to SQL at all.
Regards
Colin Dawson
www.cjdawson.com|||> There's nothing wrong with giving software access to SQL Server, just make
> sure that the security is set so that it can't do anything that it
> shouldn't. You'll also need to make sure that it's not possible to inject
> stuff that you shouldn't be able to.
Thank you, that's precisely what I was looking for.

> As a different idea, maybe you should take a look at the SSIS (SQL Server
> Integration Services) This is the all new DTS replacement. Using SSIS,
you
> can pull the information direct from the file system, perform some
> transformation and insert the files into SQL. It can be setup on a
schedule
> so the entire process can be automated, and executed by SQL Server! No
need
> to give IIS and all those other nasties access to SQL at all.
If you are referring to SQL 2005, I cannot do that because I am not up to
speed on it yet, but that does sound like it is more secure.
In any case, if I am reading you correctly, it sounds like I am OK as long
as LocalSystem and NetworkService have limited permissions.
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei|||>
> If you are referring to SQL 2005, I cannot do that because I am not up to
> speed on it yet, but that does sound like it is more secure.
> In any case, if I am reading you correctly, it sounds like I am OK as long
> as LocalSystem and NetworkService have limited permissions.
>
You could do it with permissions. I wouldn't worry about not being up to
speed on SQL 2005, if you wait for that it'll be a year or so before you can
truly say that. (maybe longer!) The Integrations services are a replacement
for DTS, hence why I'm saying not to bother with it. But surely if security
is a major consideration, it's worth spending a few hours getting up to
speed on part of the SQL Server Business intelligence studio.
Specifically, it's the Integrations service project that you need to look
at.
In a nutshell you can split the task into several stages, such as read a
file, convert the format, perform some aggregations, split the data into
distinct subsets, write the data into a table. Keeping each step distinct
and seperate will allow the SSIS to split the taks up into many threads, so
you get a performance boost using multi threading, but SQL will do all the
work for you.
Regards
Colin Dawson
www.cjdawson.com

DTSWizard Doesnt show new ODBC data source?

I've installed SQL Express SP1 on a Windows 2003 server and I'm trying to get a new MySQL datasource to be recognized in the DTSWizard. A MySQL database needs to be moved over to a MS SQL server due to software requirements (which weren't looked at before the site was created). I've installed the ODBC Connector/MySQL software and created the System DSN (named "MySQL DB Import) in the Administrative Tools/Data Sources (ODBC) tool. When I start up the DTS wizard for SQL Express however, I do not get my new data source in the selection options for data sources.

I am following the instructions on this page:
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/mysql.mspx#ERJAE

What am I missing?

It is not you missing anything the DTS you got is very limited almost a copy wizard so it is not intelligent enough to move your MySQL database, so try the link below and download the eval it is good for 6 months. Remember it is the Enterprise edition so choose all components if there is a separate folder for tools install it. So you can use SQL Server integration services. Post again if you still have question. And please try to buy the no deployment developer edition it is less than $35.00. Hope this helps.

http://www.microsoft.com/downloads/details.aspx?familyid=6931fa7f-c094-49a2-a050-2d07993566ec&displaylang=en

|||

It may be that the full SQL Integration Services are dumbed down in the evaluation too. The DTS tool in the evaluation edition wouldn't allow any new data sources either. I ended up deleting the Program Files SQL directories, the registry entries (for DTS, SQL Server, anything else that was installed with it), etc. but still no go. I'm a unix admin so this is rarely touched territory for me. What I ended up doing was exporting the database (luckily it's not yet in production) via third party tool (Navicat) to individual table MS Access databases, and then importing those via the DTS tool into MS SQL Server. I just have to wait now for the programmer to convert the site.

Thanks anyways.

dts2000 migration, activex script and odbc connections help needed

Apologies if this has been covered before or if i am in the wrong place.

I am migrating some DTS2000 packages to SSIS via the migration wizard. However there is an activex script in each DTS package that connects to an AS400 to retrieve teh record count of a table for integrity checking. Under SQL server 2000 this worked fine but in SSIS it errors with "The OLE DB provider "MSADSQL" has not been registered" how do i get this to work i suspect its because this is a 32 bit dll and my new system is a 64bit sql server 05 on windows 2003. The odbc driver for the as400 has been installed also.

The activex script is as follows:

dim cn 'sql connection
dim rs 'sql recordset for the insertion of new as400 records
dim insertstr 'sql insert string
dim rs1 'sql recordset for the insertion of new as400 records
dim insertstr1 'sql insert string

set cn = createobject("ADODB.Connection")
set rs = createobject("ADODB.Recordset")

Function Main()
'set up connection for sql
cn.provider="sqloledb"
cn.commandtimeout = 3600 'timeout in seconds
cn.open %sqlserver05%, %user%, %password%

'populate temporary table in sql with recordset from as400 odbc
insertstr1 = "Insert into db.dbo.%table% select 'table name',a.* from openrowset ('MSDASQL','DRIVER={Client Access ODBC Driver (32-bit)};SYSTEM=%system name%;UID=%username%;PWD=%password%','SELECT count(*) from %table%') as a"

set rs1 = cn.execute (insertstr1)

'close all objects
cn.close
Main = DTSTaskExecResult_Success
End Function

I have since changed MSDASQL to SQLNCLI but (after errors re ad hoc distributed queries which i have enabled) i now get errors re linked servers:

ole db provider "sqlncli" for linked server "(null)" returned message "invalid connection string attrbute"

Does anyone know how i change this to work under sql server 2005. i need to resolve this quickly in order to deliver a project on time. Many thanks

Chris

I am contacting the SSIS team but I suspect that you need to run the 32-bit version of SSIS since - as you pointed out - the ODBC driver is a 32-bit DLL, somehwat similar to the case discussed at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=167907&SiteID=1.

|||

I confirmed: if there is only 32-bit ODBC driver, you need to run the package using 32-bit runtime.

DTS, driver ODBC for Btrieve

Hi,
I need transformation data from files Btrieve (.dt) to any other formats. Where i can download driver ODBC or OLE DB for Btrieve?
And how install this driver?
Thank.See the vendors list (http://www.sqlsummit.com/oledbVen.htm) and get it.|||Originally posted by Satya
See the vendors list (http://www.sqlsummit.com/oledbVen.htm) and get it.
You have already used this Vendors list?
Exist of the shareware or freeware drivers?|||I've used Data Direct Technologies and for the shareware ensure to test them before deploying on production server.

Freeware/shareware are easy to get but make sure there is no security threat to the server.|||Originally posted by Satya
I've used Data Direct Technologies and for the shareware ensure to test them before deploying on production server.

Freeware/shareware are easy to get but make sure there is no security threat to the server.
What to do Data Direct Technologies? This is alternative DTS?
Give me links for downloads Data Direct Technologies, pls.|||I think you're not interested in the referred link, where this http://www.datadirect-technologies.com/ link is listed there.

Originally posted by Cancer
What to do Data Direct Technologies? This is alternative DTS?
Give me links for downloads Data Direct Technologies, pls.|||I looked only those links, which support Btrieve.
I have not found still shareware/freeware driver.

Thank for discussion|||Then may contact vendors listed, for further information.

DTS wont work with Ole DB provider but will with odbc

I started another thread thinking this migh have something to do with an upgrade from trial version to enterprise version

So everything seems to be working (haven't tested alot) but now I can't run DTS!

I get a weird error.

so then I tried ODBC and it works :[sp3

DTS Truncates data to destination

Hi all
I am using SQL Server 2000, since I dont have OLEDB provider for
Postgres, and SSIS does not support ODBC connection for migartion of
data.
I want to move data from my source tables to other database, for about
1000 tables.
Problem is that size of columns in source is large while the size of
columns in destination is small. I dont have control over desing of
destination database.
When I migrate data from source to destination, DTS truncate data to
size of dstination column and migarate data, but does not show any
warning that data is truncated.
If I will get warning it will be definately good for us to find out
tables in which data is truncated.
Because this we are not able to find out for which columns data is
truncated, its a big headache for the developers.
RegardsHi
http://pgfoundry.org/projects/oledb seems to be the project that is building
an OLEDB driver for progress! You may want to try using an interim file
format exported using SSIS (say Excel) or possibly use a linked server
instead.
John
"shahdharti@.gmail.com" wrote:

> Hi all
> I am using SQL Server 2000, since I dont have OLEDB provider for
> Postgres, and SSIS does not support ODBC connection for migartion of
> data.
> I want to move data from my source tables to other database, for about
> 1000 tables.
> Problem is that size of columns in source is large while the size of
> columns in destination is small. I dont have control over desing of
> destination database.
> When I migrate data from source to destination, DTS truncate data to
> size of dstination column and migarate data, but does not show any
> warning that data is truncated.
> If I will get warning it will be definately good for us to find out
> tables in which data is truncated.
> Because this we are not able to find out for which columns data is
> truncated, its a big headache for the developers.
>
> Regards
>|||Hi
http://pgfoundry.org/projects/oledb seems to be the project that is building
an OLEDB driver for progress! You may want to try using an interim file
format exported using SSIS (say Excel) or possibly use a linked server
instead.
John
"shahdharti@.gmail.com" wrote:

> Hi all
> I am using SQL Server 2000, since I dont have OLEDB provider for
> Postgres, and SSIS does not support ODBC connection for migartion of
> data.
> I want to move data from my source tables to other database, for about
> 1000 tables.
> Problem is that size of columns in source is large while the size of
> columns in destination is small. I dont have control over desing of
> destination database.
> When I migrate data from source to destination, DTS truncate data to
> size of dstination column and migarate data, but does not show any
> warning that data is truncated.
> If I will get warning it will be definately good for us to find out
> tables in which data is truncated.
> Because this we are not able to find out for which columns data is
> truncated, its a big headache for the developers.
>
> Regards
>

DTS Truncates data to destination

Hi all
I am using SQL Server 2000, since I dont have OLEDB provider for
Postgres, and SSIS does not support ODBC connection for migartion of
data.
I want to move data from my source tables to other database, for about
1000 tables.
Problem is that size of columns in source is large while the size of
columns in destination is small. I dont have control over desing of
destination database.
When I migrate data from source to destination, DTS truncate data to
size of dstination column and migarate data, but does not show any
warning that data is truncated.
If I will get warning it will be definately good for us to find out
tables in which data is truncated.
Because this we are not able to find out for which columns data is
truncated, its a big headache for the developers.
RegardsHi
http://pgfoundry.org/projects/oledb seems to be the project that is building
an OLEDB driver for progress! You may want to try using an interim file
format exported using SSIS (say Excel) or possibly use a linked server
instead.
John
"shahdharti@.gmail.com" wrote:
> Hi all
> I am using SQL Server 2000, since I dont have OLEDB provider for
> Postgres, and SSIS does not support ODBC connection for migartion of
> data.
> I want to move data from my source tables to other database, for about
> 1000 tables.
> Problem is that size of columns in source is large while the size of
> columns in destination is small. I dont have control over desing of
> destination database.
> When I migrate data from source to destination, DTS truncate data to
> size of dstination column and migarate data, but does not show any
> warning that data is truncated.
> If I will get warning it will be definately good for us to find out
> tables in which data is truncated.
> Because this we are not able to find out for which columns data is
> truncated, its a big headache for the developers.
>
> Regards
>

dts transform task failing when using IBM db2 odbc driver..

The thing is I am using a DTS package to get data from db2 residing on a s390-mainframe and put it in a sql 2000 db on windows 2000 server..

I have the odbc driver that the server guys gave me..I installed it and then run a batch pgm, which i think does the database set up...in short i set up the DSN's in my local machine..I can use the dsn when i use the sql client...

I can't create a new package and then complete the task..Problem is when i try set up a transform task, i get a memory error...it says that the instruction referenced a memory location that can't be read...

So what i do is i use the import task in sql...which inturn uses the same odbc connection and runs the query on db2..inserts the results into a table in sql..then save the package...Only problem is that i can't edit the transorm task...same memory error...

Any idea why this happens ?? I would like to see how i can get past this using Odbc...What version of the driver are you using? IBM posts hotfixes and patches on their website for their drivers; you may be able to find a fix for the one you are using.

In particular I remember a hotfix for their AS/400 V5R1 driver that fixed an issue I was having.

Regards,

hmscott|||think it is ==>
Version: 7, Release: 2, Modification: 3, Service Level: WR21254

DTS transfert AS400 --> SQL Server 2000

I have an ODBC link to DB2 Database. I can see the values of the DB2's
tables in Access but not in SQL Server DTS.
IN DTS, I connect the Source but when i want to see the values in the
Data transformation task, i have this message :

HResult of 0x90040e37 (-2147217865) returned. Erreur inattendue. Un
rsultat d'erreur a t renvoy sans message d'erreur.

Someone have a solution?dchaumeil@.yahoo.fr (David Chaumeil) wrote in message news:<89a69082.0307212321.7a291786@.posting.google.com>...
> I have an ODBC link to DB2 Database. I can see the values of the DB2's
> tables in Access but not in SQL Server DTS.
> IN DTS, I connect the Source but when i want to see the values in the
> Data transformation task, i have this message :
> HResult of 0x90040e37 (-2147217865) returned. Erreur inattendue. Un
> rsultat d'erreur a t renvoy sans message d'erreur.
> Someone have a solution?

What version is your client access ?

I had the similar error message before with older version client
access and in the ODBC configuration, you need to check the setting of
those parameters.

Good Luck !

DTS to Lotus notes

DTS to Lotus notes

I must import/export some data from SQL Server to Lotus Notes.
I downloaded and installed NotesSQL ODBC drivers.
I met no problem importing from a Lotus Notes view to an SQL Server table: I used DTS and everything succeded.
But I can't do the reverse process (exporting from SQL Server to Lotus Notes): DTS keeps on giving an error without description and it fails.
Does anybody know how to export a table or a view from SQL Server to Lotus Notes using DTS?

Thanks in advance.Are you trying to setup a daily process, or is it a 1 time thing?

Do you have Notespump or Notestrix?

And as much as they protest, Lotus Notes is NOT a database...

Sorry...I got carried away...

And what do you mean...are you trying 2 way replication?|||Originally posted by Brett Kaiser
Are you trying to setup a daily process, or is it a 1 time thing?

Do you have Notespump or Notestrix?

And as much as they protest, Lotus Notes is NOT a database...

Sorry...I got carried away...

And what do you mean...are you trying 2 way replication?

Thanks for the reply. This would be a weekly process that I would like to setup and schedule via DTS. I would agree that notes is not a database by definition. I would just like to automate this if possible. It is a very small dataset based on an SQL query. Do I have a bad version of NotesSQL that only works one way?! I don't have Notespump or Notestrix. Wouldn't those apps be a bit overkill? Thanks! - JB|||I haven't done this...but I'm going to try it...got a link for the driver?

Also, how do you authenticate?

Maybe it's a permissions issue...|||Originally posted by Brett Kaiser
I haven't done this...but I'm going to try it...got a link for the driver?

Also, how do you authenticate?

Maybe it's a permissions issue...

The site is: www.lotus.com/notessql

The owner of the DB has given me read/write
permission on the DB. Each time DTS attempts
to read or write to the .nsf, I am prompted for
my lotus notes password and it is accepted.|||Still looking

Found this

http://www.lotus.com/products/rnext.nsf/873769A79D9C5B2285256A0800720B96/F8BA31E9F7BDEC3A85256C4700667625?OpenDocument

Does it have to be installed on the server, or can it be installed on the client?

I guess where ever DTS is running, no?|||Originally posted by Brett Kaiser
Still looking

Found this

http://www.lotus.com/products/rnext.nsf/873769A79D9C5B2285256A0800720B96/F8BA31E9F7BDEC3A85256C4700667625?OpenDocument

Does it have to be installed on the server, or can it be installed on the client?

I guess where ever DTS is running, no?

Yes. I think you would want to install it on the server. You will then be permitted to setup an odbc connection there to an nsf file.|||You can install on the client...just did it...

Bam shows up in my source selection list...

Now I gotta find a notes server to link to...

Did you see the user manual after the install?|||I've reviewed the "help" html doc a bit. It seems to talk more about extracting data to another DB.|||The site is: www.lotus.com/notessql

...Each time DTS attempts to read or write to the .nsf, I am prompted for
my lotus notes password and it is accepted.

Don't want this to happen every time? Go into your registry under HKLM->Software->ODBC->ODBC.INI, then find the entry for your connection. Add a new string called SuppressUID and set it to 1. You won't get prompted anymore. You do have to do this for all of your Notes connections though.