Showing posts with label integrated. Show all posts
Showing posts with label integrated. Show all posts

Wednesday, March 21, 2012

Minimal required DLLS for Named Pipes connection?

I have a work around for an application use Integrated Security
instead of SQL Security (which is great). I need to use named pipes
for this to work.
I only got it to work after I did a SQL 2005 Connectivity and Client
Tools install which
installed everything but the Server services. Boss doesn't like this
approach, wants minimal install.
My questions:
Are there just a few DLLs that I need to connect to SQL Server with
named pipes only?
Do I need to Register the DLLs using REGSRV32.EXE?
Thanks
ErikYou can probably get this to work with only installing the client
connectivity. I wouldn't try to hack it.
Jason Massie
http://statisticsio.com
"Erik G" <info@.fdaregulatory.com> wrote in message
news:1194885570.885338.225030@.v3g2000hsg.googlegroups.com...
>I have a work around for an application use Integrated Security
> instead of SQL Security (which is great). I need to use named pipes
> for this to work.
> I only got it to work after I did a SQL 2005 Connectivity and Client
> Tools install which
> installed everything but the Server services. Boss doesn't like this
> approach, wants minimal install.
> My questions:
> Are there just a few DLLs that I need to connect to SQL Server with
> named pipes only?
> Do I need to Register the DLLs using REGSRV32.EXE?
> Thanks
> Erik
>

Minimal required DLLS for Named Pipes connection?

I have a work around for an application use Integrated Security
instead of SQL Security (which is great). I need to use named pipes
for this to work.
I only got it to work after I did a SQL 2005 Connectivity and Client
Tools install which
installed everything but the Server services. Boss doesn't like this
approach, wants minimal install.
My questions:
Are there just a few DLLs that I need to connect to SQL Server with
named pipes only?
Do I need to Register the DLLs using REGSRV32.EXE?
Thanks
Erik
You can probably get this to work with only installing the client
connectivity. I wouldn't try to hack it.
Jason Massie
http://statisticsio.com
"Erik G" <info@.fdaregulatory.com> wrote in message
news:1194885570.885338.225030@.v3g2000hsg.googlegro ups.com...
>I have a work around for an application use Integrated Security
> instead of SQL Security (which is great). I need to use named pipes
> for this to work.
> I only got it to work after I did a SQL 2005 Connectivity and Client
> Tools install which
> installed everything but the Server services. Boss doesn't like this
> approach, wants minimal install.
> My questions:
> Are there just a few DLLs that I need to connect to SQL Server with
> named pipes only?
> Do I need to Register the DLLs using REGSRV32.EXE?
> Thanks
> Erik
>
sql

Wednesday, March 7, 2012

Migration from sybase 8.0 to mssql server 2005

Hi all,

Here i had a task to migrate sybase 8.0 database to mssqlserver 2005 .how can i migrate this using INTEGRATED SERVICES (SSIS) or any other options. .Please try to provide some basical info because i am new to sybase versions.

Maybe these article will help:
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part2/c0661.mspx
http://www.microsoft.com/technet/itsolutions/migration/unix/sybsqlsv/default.mspx
http://www.microsoft.com/downloads/details.aspx?familyid=E7541305-891F-494A-B58B-2EED819C4411&displaylang=en
http://www.microsoft.com/sql/prodinfo/compare/sybase.mspx
http://www.devarticles.com/c/a/SQL-Server/Migrating-from-Sybase-to-SQL-Server/|||Basically that artical explaining migration from sybase|unix to sqlserver 2000 But not mssql server 2005 ,i gone through that article before but i did not find any help from that please can you make it clear.