Showing posts with label client. Show all posts
Showing posts with label client. Show all posts

Friday, March 30, 2012

How to attach a db_file with problems?

A database goes "SUSPECT" the client deatach de DB. later it tries to
reatach it but he gets an error. I tried to copy the file to other disk but
I get an error from windows saying that a cyclic error in the disk prevent
the copy. Is there any way to attach a file with problems? just in order to
save at least some of the data?You can create a new database with the same name, using the same data file
and log file names. Then shut down SQL Server and copy your "bad" files
over the top of these new files. When SQL Server starts the database will
once again be suspect. You can then put the database in emergency mode
(status 32768) and recycle SQL Server. At this point you should be able to
at least salvage some of the data, may be all depending on the rason it
went suspect.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi,
To add on, I had a identical instance where I followed the same procedure as
Rand suggested , after that,
1. The Datbase was able to open in Emergency mode (32768)
2. I was not able to take a backup.
What I did,
1. Create a new database
2. Script out all objects in seperate files
3. Executed the user defined types(UDT) and Table creation script in new
database
4. Run DTS to transfer all data from old to new database ( U can also use
BCP OUT /IN)
5. Executed the Indexe creation script
6. Executed all the other object creation script
After these steps I did a comparison of old and new database and FYI, I lost
few pieces of data which I asked the users to re enter.
Thanks
Hari
MCDBA
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:M3yLU1E6DHA.2768@.cpmsftngxa07.phx.gbl...
quote:

> You can create a new database with the same name, using the same data file
> and log file names. Then shut down SQL Server and copy your "bad" files
> over the top of these new files. When SQL Server starts the database will
> once again be suspect. You can then put the database in emergency mode
> (status 32768) and recycle SQL Server. At this point you should be able to
> at least salvage some of the data, may be all depending on the rason it
> went suspect.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

How to attach a db_file with problems?

A database goes "SUSPECT" the client deatach de DB. later it tries to
reatach it but he gets an error. I tried to copy the file to other disk but
I get an error from windows saying that a cyclic error in the disk prevent
the copy. Is there any way to attach a file with problems? just in order to
save at least some of the data?You can create a new database with the same name, using the same data file
and log file names. Then shut down SQL Server and copy your "bad" files
over the top of these new files. When SQL Server starts the database will
once again be suspect. You can then put the database in emergency mode
(status 32768) and recycle SQL Server. At this point you should be able to
at least salvage some of the data, may be all depending on the rason it
went suspect.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi,
To add on, I had a identical instance where I followed the same procedure as
Rand suggested , after that,
1. The Datbase was able to open in Emergency mode (32768)
2. I was not able to take a backup.
What I did,
1. Create a new database
2. Script out all objects in seperate files
3. Executed the user defined types(UDT) and Table creation script in new
database
4. Run DTS to transfer all data from old to new database ( U can also use
BCP OUT /IN)
5. Executed the Indexe creation script
6. Executed all the other object creation script
After these steps I did a comparison of old and new database and FYI, I lost
few pieces of data which I asked the users to re enter.
Thanks
Hari
MCDBA
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:M3yLU1E6DHA.2768@.cpmsftngxa07.phx.gbl...
> You can create a new database with the same name, using the same data file
> and log file names. Then shut down SQL Server and copy your "bad" files
> over the top of these new files. When SQL Server starts the database will
> once again be suspect. You can then put the database in emergency mode
> (status 32768) and recycle SQL Server. At this point you should be able to
> at least salvage some of the data, may be all depending on the rason it
> went suspect.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>sql

Wednesday, March 7, 2012

How to add a Network Library Config (Server Alias) using Transact-

Hi,
I can create an Alias for a remote server fine using the Client Network
Utility (Alias tab, Add -> "Add Netwok Library Configuration" - TCP/IP,
Server name = IP Address, specify port number).
... how can I accomplish the same thing using TRANSACT-SQL so I can create a
script which will do this for my customer.
Thanks in advance, J
Jamie Clancy
Ulysses Systems, London
I don't think this is in TSQL's scope of functionality--it's a networking /
DNS configuration, not a SQL Server config. It seems to me you might try
changing the Hosts file on the client system--it can do about the same
thing...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Jamie_C" <jclancy@.ulysses-systems.com.removethisbit> wrote in message
news:AD9F9920-B4CF-45D0-84CF-ECE22B0142B5@.microsoft.com...
> Hi,
> I can create an Alias for a remote server fine using the Client Network
> Utility (Alias tab, Add -> "Add Netwok Library Configuration" - TCP/IP,
> Server name = IP Address, specify port number).
> ... how can I accomplish the same thing using TRANSACT-SQL so I can create
> a
> script which will do this for my customer.
> Thanks in advance, J
> --
> Jamie Clancy
> Ulysses Systems, London
|||Thanks Bill.
I discovered that I can successfully connect directly using a connection
string which contains the IP address and port number instead, so I don't need
to create an alias after all.
Here's an example:
Provider=SQLOLEDB.1;Password=MyPass;User ID=MyUser;Initial
Catalog=MyDBName;Server=xxx.xxx.xxx.xxx,yyyy
where xxx.xxx.xxx.xxx is the server IP adress and yyyy is the port number
(e.g. 1433 usually for SQL Server)
Jamie Clancy
Ulysses Systems, London
"William (Bill) Vaughn" wrote:

> I don't think this is in TSQL's scope of functionality--it's a networking /
> DNS configuration, not a SQL Server config. It seems to me you might try
> changing the Hosts file on the client system--it can do about the same
> thing...
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Jamie_C" <jclancy@.ulysses-systems.com.removethisbit> wrote in message
> news:AD9F9920-B4CF-45D0-84CF-ECE22B0142B5@.microsoft.com...
>
>
|||Yes but... connecting via the public web can be problematic. Most shops
don't want to expose the server to the relentless pounding they get from
hackers all over the world trying to break in. I hope this address begins
with 192.168... Of course 80% of hacking comes from within the firewall. I
hope you have a strong SA password.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Jamie_C" <jclancy@.ulysses-systems.com.removethisbit> wrote in message
news:D3FC3B27-9663-40B3-953F-B6F3E5644CE5@.microsoft.com...[vbcol=seagreen]
> Thanks Bill.
> I discovered that I can successfully connect directly using a connection
> string which contains the IP address and port number instead, so I don't
> need
> to create an alias after all.
> Here's an example:
> Provider=SQLOLEDB.1;Password=MyPass;User ID=MyUser;Initial
> Catalog=MyDBName;Server=xxx.xxx.xxx.xxx,yyyy
> where xxx.xxx.xxx.xxx is the server IP adress and yyyy is the port number
> (e.g. 1433 usually for SQL Server)
> --
> Jamie Clancy
> Ulysses Systems, London
>
> "William (Bill) Vaughn" wrote:

How to add a Network Library Config (Server Alias) using Transact-

Hi,
I can create an Alias for a remote server fine using the Client Network
Utility (Alias tab, Add -> "Add Netwok Library Configuration" - TCP/IP,
Server name = IP Address, specify port number).
... how can I accomplish the same thing using TRANSACT-SQL so I can create
a
script which will do this for my customer.
Thanks in advance, J
Jamie Clancy
Ulysses Systems, LondonI don't think this is in TSQL's scope of functionality--it's a networking /
DNS configuration, not a SQL Server config. It seems to me you might try
changing the Hosts file on the client system--it can do about the same
thing...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Jamie_C" <jclancy@.ulysses-systems.com.removethisbit> wrote in message
news:AD9F9920-B4CF-45D0-84CF-ECE22B0142B5@.microsoft.com...
> Hi,
> I can create an Alias for a remote server fine using the Client Network
> Utility (Alias tab, Add -> "Add Netwok Library Configuration" - TCP/IP,
> Server name = IP Address, specify port number).
> ... how can I accomplish the same thing using TRANSACT-SQL so I can create
> a
> script which will do this for my customer.
> Thanks in advance, J
> --
> Jamie Clancy
> Ulysses Systems, London

Sunday, February 19, 2012

How to access to excel,csv or other formatted file using OLE DB(SQL Native Client)?

Hi~.

First, is it possible to access(read/write) to the excel,csv or my-own-formatted file using OLE DB(SQL Native Client)?

If possible, how?

You can create linked server to the excel spreadsheet as shown in : http://msdn2.microsoft.com/en-us/library/ms190479.aspx

You can use OpenRowset (http://msdn2.microsoft.com/en-us/library/ms190312.aspx)

or OpenQuery( http://msdn2.microsoft.com/en-us/library/ms188427.aspx) to retrieve data.

Providing an example using VB6 / ADO using SQLNCLI

Sub main()

Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset

cn.Open "Provider=SQLNCLI;Data Source=<datasourcename>;Integrated Security=SSPI;"

'Refer to table using linked server
rs.Open "select * from <linkedsrvname>...TestTable", cn

'OpenRowset
Set rs = cn.Execute("select * from OpenRowset('Microsoft.Jet.OLEDB.4.0', 'Excel 8.0;Database=c:\TestBook.xls','select * from [TestTable]')")

'OpenQuery
Set rs = cn.Execute("select * from OpenQuery(ExcelShare,'select * from TestTable')")

While Not rs.EOF
For i = 0 To rs.Fields.Count - 1
MsgBox rs.Fields.Item(i)
Next i
rs.MoveNext
Wend

Set rs = Nothing
cn.Close

End Sub

How to access SQL Server on another domain with Windows authentica

I have two computers, client and server. The client is running Windows 2000
Professional and is in a workgroup, say "MyWorkgroup". The server is runnin
g
Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
The server has SQL Server 2000 Standard Edition with SP3a installed and is
using Windows authentication. What I need is to logon to the client as some
generic local administrator user and access SQL Server on the server using
Windows Authentication (i.e. domain user)? How can I do this? Impersonatin
g
a domain user on the server from the client (which is not in the domain, jus
t
in a workgroup)? But how can I do this kind of impersonation? BTW, the
client is written in C++.NET using Windows Forms and accessing SQL Server
using ADO.NET.
Thank you.First try setting the same user and password on both pc and server
login to the pc with the new you name.
Second to your seft to the domain in admin group
I hope this Helps
"CyberDigger" <CyberDigger@.discussions.microsoft.com> wrote in message
news:7DD371D4-22DB-465A-89A3-B3F5DEDEA474@.microsoft.com...
> I have two computers, client and server. The client is running Windows
2000
> Professional and is in a workgroup, say "MyWorkgroup". The server is
running
> Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
> The server has SQL Server 2000 Standard Edition with SP3a installed and is
> using Windows authentication. What I need is to logon to the client as
some
> generic local administrator user and access SQL Server on the server using
> Windows Authentication (i.e. domain user)? How can I do this?
Impersonating
> a domain user on the server from the client (which is not in the domain,
just
> in a workgroup)? But how can I do this kind of impersonation? BTW, the
> client is written in C++.NET using Windows Forms and accessing SQL Server
> using ADO.NET.
> Thank you.|||Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.security:23830 microso
ft.public.sqlserver.server:376048 microsoft.public.dotnet.security:9420 micr
osoft.public.dotnet.datatools:1593 microsoft.public.sqlserver.programming:49
9446
Your options are:
1) Set the passwords and usernames the same on the local machine in the
workgroup and the domain
2) Use named pipes to connect and Pre-Authenticate (like with a net use
\\server /user:domain\user password) before connecting to sql
3) use sql std logins

How to access SQL Server on another domain with Windows authentica

I have two computers, client and server. The client is running Windows 2000
Professional and is in a workgroup, say "MyWorkgroup". The server is running
Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
The server has SQL Server 2000 Standard Edition with SP3a installed and is
using Windows authentication. What I need is to logon to the client as some
generic local administrator user and access SQL Server on the server using
Windows Authentication (i.e. domain user)? How can I do this? Impersonating
a domain user on the server from the client (which is not in the domain, just
in a workgroup)? But how can I do this kind of impersonation? BTW, the
client is written in C++.NET using Windows Forms and accessing SQL Server
using ADO.NET.
Thank you.
CyberDigger,
so let me understand your problem clearly first.
One is a server running Sql Server (Win 2k3) This is in MyDoman.
Second is a client running your winforms app. (Win2k) This is in
MyWorkGroup.
You want -- to connect to the sql server database, using the credentials
used to log on to the local client box?
I don't think that's do-able since the anything on the domain will never be
able to validate locally entered credentials on the client. The best you can
do is to remote over to the win2k3 server itself and something running on
the win2k3 server with sufficient privelleges in the domain acts as your
data layer - that might be an acceptable solution?
I hope I'm wrong though
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"CyberDigger" <CyberDigger@.discussions.microsoft.com> wrote in message
news:3B3A9B3F-B2F5-4924-B0A5-B53D41A10FD1@.microsoft.com...
>I have two computers, client and server. The client is running Windows
>2000
> Professional and is in a workgroup, say "MyWorkgroup". The server is
> running
> Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
> The server has SQL Server 2000 Standard Edition with SP3a installed and is
> using Windows authentication. What I need is to logon to the client as
> some
> generic local administrator user and access SQL Server on the server using
> Windows Authentication (i.e. domain user)? How can I do this?
> Impersonating
> a domain user on the server from the client (which is not in the domain,
> just
> in a workgroup)? But how can I do this kind of impersonation? BTW, the
> client is written in C++.NET using Windows Forms and accessing SQL Server
> using ADO.NET.
> Thank you.
|||Perhaps you can setup a linked server (which includes the remote
credentials) and use that in the server-side join...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Sahil Malik" <contactmethrumyblog@.nospam.com> wrote in message
news:%23ZkzzIh9EHA.2676@.TK2MSFTNGP12.phx.gbl...
> CyberDigger,
> so let me understand your problem clearly first.
> One is a server running Sql Server (Win 2k3) This is in MyDoman.
> Second is a client running your winforms app. (Win2k) This is in
> MyWorkGroup.
> You want -- to connect to the sql server database, using the credentials
> used to log on to the local client box?
> I don't think that's do-able since the anything on the domain will never
> be able to validate locally entered credentials on the client. The best
> you can do is to remote over to the win2k3 server itself and something
> running on the win2k3 server with sufficient privelleges in the domain
> acts as your data layer - that might be an acceptable solution?
> I hope I'm wrong though
> - Sahil Malik
> http://dotnetjunkies.com/weblog/sahilmalik
>
>
> "CyberDigger" <CyberDigger@.discussions.microsoft.com> wrote in message
> news:3B3A9B3F-B2F5-4924-B0A5-B53D41A10FD1@.microsoft.com...
>
|||Yeah that's a good idea.
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:exowOHr9EHA.3708@.TK2MSFTNGP14.phx.gbl...
> Perhaps you can setup a linked server (which includes the remote
> credentials) and use that in the server-side join...
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> "Sahil Malik" <contactmethrumyblog@.nospam.com> wrote in message
> news:%23ZkzzIh9EHA.2676@.TK2MSFTNGP12.phx.gbl...
>
|||Here is a way you can do it:
On the server, set up a local NT/2000 account with the same login name and
password as used to log into the workstation.
Give that account permission using NT Authentication.
Use NT Authentication on clients from the workstation.
I will caution you that when you do this, if you change your password at the
local workstation, you will get logon errors unless you synchronize your
password on the server.
"CyberDigger" wrote:

> I have two computers, client and server. The client is running Windows 2000
> Professional and is in a workgroup, say "MyWorkgroup". The server is running
> Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
> The server has SQL Server 2000 Standard Edition with SP3a installed and is
> using Windows authentication. What I need is to logon to the client as some
> generic local administrator user and access SQL Server on the server using
> Windows Authentication (i.e. domain user)? How can I do this? Impersonating
> a domain user on the server from the client (which is not in the domain, just
> in a workgroup)? But how can I do this kind of impersonation? BTW, the
> client is written in C++.NET using Windows Forms and accessing SQL Server
> using ADO.NET.
> Thank you.

How to access SQL Server on another domain with Windows authentica

I have two computers, client and server. The client is running Windows 2000
Professional and is in a workgroup, say "MyWorkgroup". The server is running
Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
The server has SQL Server 2000 Standard Edition with SP3a installed and is
using Windows authentication. What I need is to logon to the client as some
generic local administrator user and access SQL Server on the server using
Windows Authentication (i.e. domain user)? How can I do this? Impersonating
a domain user on the server from the client (which is not in the domain, just
in a workgroup)? But how can I do this kind of impersonation? BTW, the
client is written in C++.NET using Windows Forms and accessing SQL Server
using ADO.NET.
Thank you.
First try setting the same user and password on both pc and server
login to the pc with the new you name.
Second to your seft to the domain in admin group
I hope this Helps
"CyberDigger" <CyberDigger@.discussions.microsoft.com> wrote in message
news:7DD371D4-22DB-465A-89A3-B3F5DEDEA474@.microsoft.com...
> I have two computers, client and server. The client is running Windows
2000
> Professional and is in a workgroup, say "MyWorkgroup". The server is
running
> Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
> The server has SQL Server 2000 Standard Edition with SP3a installed and is
> using Windows authentication. What I need is to logon to the client as
some
> generic local administrator user and access SQL Server on the server using
> Windows Authentication (i.e. domain user)? How can I do this?
Impersonating
> a domain user on the server from the client (which is not in the domain,
just
> in a workgroup)? But how can I do this kind of impersonation? BTW, the
> client is written in C++.NET using Windows Forms and accessing SQL Server
> using ADO.NET.
> Thank you.
|||Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.security:23830 microsoft.public.sqlserver.server:376048 microsoft.public.dotnet.security:9420 microsoft.public.dotnet.datatools:1593 microsoft.public.sqlserver.programming:499446
Your options are:
1) Set the passwords and usernames the same on the local machine in the
workgroup and the domain
2) Use named pipes to connect and Pre-Authenticate (like with a net use
\\server /user:domain\user password) before connecting to sql
3) use sql std logins

How to access SQL Server on another domain with Windows authentica

I have two computers, client and server. The client is running Windows 2000
Professional and is in a workgroup, say "MyWorkgroup". The server is running
Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
The server has SQL Server 2000 Standard Edition with SP3a installed and is
using Windows authentication. What I need is to logon to the client as some
generic local administrator user and access SQL Server on the server using
Windows Authentication (i.e. domain user)? How can I do this? Impersonating
a domain user on the server from the client (which is not in the domain, just
in a workgroup)? But how can I do this kind of impersonation? BTW, the
client is written in C++.NET using Windows Forms and accessing SQL Server
using ADO.NET.
Thank you.First try setting the same user and password on both pc and server
login to the pc with the new you name.
Second to your seft to the domain in admin group
I hope this Helps
"CyberDigger" <CyberDigger@.discussions.microsoft.com> wrote in message
news:7DD371D4-22DB-465A-89A3-B3F5DEDEA474@.microsoft.com...
> I have two computers, client and server. The client is running Windows
2000
> Professional and is in a workgroup, say "MyWorkgroup". The server is
running
> Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
> The server has SQL Server 2000 Standard Edition with SP3a installed and is
> using Windows authentication. What I need is to logon to the client as
some
> generic local administrator user and access SQL Server on the server using
> Windows Authentication (i.e. domain user)? How can I do this?
Impersonating
> a domain user on the server from the client (which is not in the domain,
just
> in a workgroup)? But how can I do this kind of impersonation? BTW, the
> client is written in C++.NET using Windows Forms and accessing SQL Server
> using ADO.NET.
> Thank you.|||Your options are:
1) Set the passwords and usernames the same on the local machine in the
workgroup and the domain
2) Use named pipes to connect and Pre-Authenticate (like with a net use
\\server /user:domain\user password) before connecting to sql
3) use sql std logins

How to access SQL Server on another domain with Windows authentica

I have two computers, client and server. The client is running Windows 2000
Professional and is in a workgroup, say "MyWorkgroup". The server is runnin
g
Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
The server has SQL Server 2000 Standard Edition with SP3a installed and is
using Windows authentication. What I need is to logon to the client as some
generic local administrator user and access SQL Server on the server using
Windows Authentication (i.e. domain user)? How can I do this? Impersonatin
g
a domain user on the server from the client (which is not in the domain, jus
t
in a workgroup)? But how can I do this kind of impersonation? BTW, the
client is written in C++.NET using Windows Forms and accessing SQL Server
using ADO.NET.
Thank you.CyberDigger,
so let me understand your problem clearly first.
One is a server running Sql Server (Win 2k3) This is in MyDoman.
Second is a client running your winforms app. (Win2k) This is in
MyWorkGroup.
You want -- to connect to the sql server database, using the credentials
used to log on to the local client box'
I don't think that's do-able since the anything on the domain will never be
able to validate locally entered credentials on the client. The best you can
do is to remote over to the win2k3 server itself and something running on
the win2k3 server with sufficient privelleges in the domain acts as your
data layer - that might be an acceptable solution?
I hope I'm wrong though
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"CyberDigger" <CyberDigger@.discussions.microsoft.com> wrote in message
news:3B3A9B3F-B2F5-4924-B0A5-B53D41A10FD1@.microsoft.com...
>I have two computers, client and server. The client is running Windows
>2000
> Professional and is in a workgroup, say "MyWorkgroup". The server is
> running
> Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
> The server has SQL Server 2000 Standard Edition with SP3a installed and is
> using Windows authentication. What I need is to logon to the client as
> some
> generic local administrator user and access SQL Server on the server using
> Windows Authentication (i.e. domain user)? How can I do this?
> Impersonating
> a domain user on the server from the client (which is not in the domain,
> just
> in a workgroup)? But how can I do this kind of impersonation? BTW, the
> client is written in C++.NET using Windows Forms and accessing SQL Server
> using ADO.NET.
> Thank you.|||Perhaps you can setup a linked server (which includes the remote
credentials) and use that in the server-side join...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Sahil Malik" <contactmethrumyblog@.nospam.com> wrote in message
news:%23ZkzzIh9EHA.2676@.TK2MSFTNGP12.phx.gbl...
> CyberDigger,
> so let me understand your problem clearly first.
> One is a server running Sql Server (Win 2k3) This is in MyDoman.
> Second is a client running your winforms app. (Win2k) This is in
> MyWorkGroup.
> You want -- to connect to the sql server database, using the credentials
> used to log on to the local client box'
> I don't think that's do-able since the anything on the domain will never
> be able to validate locally entered credentials on the client. The best
> you can do is to remote over to the win2k3 server itself and something
> running on the win2k3 server with sufficient privelleges in the domain
> acts as your data layer - that might be an acceptable solution?
> I hope I'm wrong though
> - Sahil Malik
> http://dotnetjunkies.com/weblog/sahilmalik
>
>
> "CyberDigger" <CyberDigger@.discussions.microsoft.com> wrote in message
> news:3B3A9B3F-B2F5-4924-B0A5-B53D41A10FD1@.microsoft.com...
>|||Yeah that's a good idea.
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:exowOHr9EHA.3708@.TK2MSFTNGP14.phx.gbl...
> Perhaps you can setup a linked server (which includes the remote
> credentials) and use that in the server-side join...
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> "Sahil Malik" <contactmethrumyblog@.nospam.com> wrote in message
> news:%23ZkzzIh9EHA.2676@.TK2MSFTNGP12.phx.gbl...
>|||Here is a way you can do it:
On the server, set up a local NT/2000 account with the same login name and
password as used to log into the workstation.
Give that account permission using NT Authentication.
Use NT Authentication on clients from the workstation.
I will caution you that when you do this, if you change your password at the
local workstation, you will get logon errors unless you synchronize your
password on the server.
"CyberDigger" wrote:

> I have two computers, client and server. The client is running Windows 20
00
> Professional and is in a workgroup, say "MyWorkgroup". The server is runn
ing
> Windows Server 2003 Standard Edition and is in a domain, say "MyDomain".
> The server has SQL Server 2000 Standard Edition with SP3a installed and is
> using Windows authentication. What I need is to logon to the client as so
me
> generic local administrator user and access SQL Server on the server using
> Windows Authentication (i.e. domain user)? How can I do this? Impersonat
ing
> a domain user on the server from the client (which is not in the domain, j
ust
> in a workgroup)? But how can I do this kind of impersonation? BTW, the
> client is written in C++.NET using Windows Forms and accessing SQL Server
> using ADO.NET.
> Thank you.