Another Domain

Hi,
We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
but that's another story).
We also have VB6 apps accessing the SQL Server using Windows authentication
.
Until now only users within our domain needed to use the apps.
There are a number of NT security groups to which we add our users depending
on their required permission levels.
However we now have a situation where users from an external domain need
access to the VB6 apps. They will also need to synchronise data using merge
replication.
Is there a way of mapping such users to our NT Security groups even though
they are members of an external domain. There will be co-operation from the
administrators of the other domain.
We would rather stick with Windows Authentication rather than Mixed Mode.
Any help greatly appreciated.
DDHi
You would need to setup trusts between the 2 domains. This is done at OS
level. Get your admins to look if it is something they really want to do. An
external company, unless it is in the same legal entity group, should not be
trusted as you have no control over their admins.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave52" wrote:

> Hi,
> We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
> but that's another story).
> We also have VB6 apps accessing the SQL Server using Windows authenticati
on.
> Until now only users within our domain needed to use the apps.
> There are a number of NT security groups to which we add our users dependi
ng
> on their required permission levels.
> However we now have a situation where users from an external domain need
> access to the VB6 apps. They will also need to synchronise data using mer
ge
> replication.
> Is there a way of mapping such users to our NT Security groups even though
> they are members of an external domain. There will be co-operation from th
e
> administrators of the other domain.
> We would rather stick with Windows Authentication rather than Mixed Mode.
> Any help greatly appreciated.
> DD
>|||The way I'd handle this is to create a local group on the SQL Server box tha
t
contains a global group from the remote domain. Then I'd simply give permiss
ions
inside SQL Server to this local group. For this to happen of course, there m
ust
be a trust between the domain that contains the SQL Server and the "external
"
domain that wants access to it.
HTH
Thomas
"Dave52" <Dave52@.discussions.microsoft.com> wrote in message
news:D40BC61F-A792-4442-BF6B-FF29BFAB9258@.microsoft.com...
> Hi,
> We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
> but that's another story).
> We also have VB6 apps accessing the SQL Server using Windows authenticati
on.
> Until now only users within our domain needed to use the apps.
> There are a number of NT security groups to which we add our users dependi
ng
> on their required permission levels.
> However we now have a situation where users from an external domain need
> access to the VB6 apps. They will also need to synchronise data using mer
ge
> replication.
> Is there a way of mapping such users to our NT Security groups even though
> they are members of an external domain. There will be co-operation from th
e
> administrators of the other domain.
> We would rather stick with Windows Authentication rather than Mixed Mode.
> Any help greatly appreciated.
> DD
>

annoying SQL Server error message

Hi,
We have developped many applications, for a major customer, connected
to the same SQL Server database. Those apps have been programmed in VB6
and VB.NET. The SQL Server is located on a dual-processor server,
running Windows 2000 Server, with 3 gigs RAM. The apps are installed on
Windows 2000 and Windows XP/SP2 client.
And the Windows 2000 client PC's, there is no problem at all. But, on
the XPs, we have, this error message popup: "Unable to load SQL Server
OLEDB provider ressource DLL. The application cannot continue". Look
like it appears randomly.
The same application, when installed on a Win2000, don't have any
problem at all. Just the damn XP machines. We cannot change the OS of
these PC's (enterprise rules).
This error is a major problem because it stops the application until
you acknowledge the error. The app is used for realtime control of a
factory, so, you see the problem...
XP workstation uses MDAC 2.8 SP1 for Windows XP SP2
2000 uses MDAC 2.6 RTM
Apps has been compiled on a MDAC 2.8 SP1 Win XP SP2 computer
How can I fix this'
thanks a lot for your help, it's really appreciated.1)Have you got the latest MDAC installation ?
2)Track down all instances of sqloledb.rll and sqloledb.dll . Make sure
they are the latest versions and match up
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"Dominic30" <gagned@.videotron.ca> wrote in message
news:1142610474.169168.15240@.i40g2000cwc.googlegroups.com...
> Hi,
> We have developped many applications, for a major customer, connected
> to the same SQL Server database. Those apps have been programmed in VB6
> and VB.NET. The SQL Server is located on a dual-processor server,
> running Windows 2000 Server, with 3 gigs RAM. The apps are installed on
> Windows 2000 and Windows XP/SP2 client.
> And the Windows 2000 client PC's, there is no problem at all. But, on
> the XPs, we have, this error message popup: "Unable to load SQL Server
> OLEDB provider ressource DLL. The application cannot continue". Look
> like it appears randomly.
> The same application, when installed on a Win2000, don't have any
> problem at all. Just the damn XP machines. We cannot change the OS of
> these PC's (enterprise rules).
> This error is a major problem because it stops the application until
> you acknowledge the error. The app is used for realtime control of a
> factory, so, you see the problem...
> XP workstation uses MDAC 2.8 SP1 for Windows XP SP2
> 2000 uses MDAC 2.6 RTM
> Apps has been compiled on a MDAC 2.8 SP1 Win XP SP2 computer
> How can I fix this'
> thanks a lot for your help, it's really appreciated.
>|||1) Yeah, I've got the latest MDAC installation. Anyway, I can't
installed another MDAC version on the XP machines, the install failed.
2) These files match up yes. I've checked all the station and it's
looks fine.
any more idea?
by the way, thanks for the reply|||In what path is the SQLOLEDB.RLL file ?
You mention that all the apps are using the same sql server. Is this though
Linked Servers?
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
"Dominic30" <gagned@.videotron.ca> wrote in message
news:1142613417.547606.39710@.z34g2000cwc.googlegroups.com...
> 1) Yeah, I've got the latest MDAC installation. Anyway, I can't
> installed another MDAC version on the XP machines, the install failed.
> 2) These files match up yes. I've checked all the station and it's
> looks fine.
> any more idea?
> by the way, thanks for the reply
>

Analyzing a Query in SQL Server

I have to duplicate a bunch of reports that were produced by a VB6 app. Now I'm using C#, ASP.net and Crystal Reports via VS2003. Each executes a stored procedure in SQL Server (before and now).

For each report I have a Stored Procedure and a View. The View's SQL code is identical to the Stored Procedure except that the two input parameters (startDate and endDate) are removed because Views don't allow parameters.

Some of the reports work perfectly right off the bat. But others are timing out. My initial test of the timing out is to just display the View. If it fails then I know that the the report engine will fail too.

So now I'm trying out the SQL Query Analyzer tool to execute the code in one of the Views. It's now at 29 minutes and still going - at least it hasn't timed out!

My question is this: Is there a way I could examine what's going on with the query to see why it's taking so long?

Robert WernerHave a look at the query execution plan in the query analyzer, do you see any bottlenecks there ? During execution you might encounter a deadlock. looking in the appropiate node in SQL Server Enterprise Manager (Current Activity) you might be able to find the blocking process.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||Jens,

Thank you for your suggestion. I've never used that Execution Plan before so just tried it out on one of the queries that's timing out. I took the liberty of taking a screen capture and posting it here:

http://pocketpollster.com/downloads/public/WBMCST11_Execution_Plan.jpg

Does this communicate anything to you?

Robert Werner
Vancouver, BC|||THe information which is sensitive while moving over the individual objects is missing for us, so its hard to tell. This is the estimated execution plan not the actual executed one, but as a rule of thumb you should have a look on the highest cost in the plan as well as actions like table scans. They are often costly if made for huge tables but are on the opposite cheaper then using indexes in smaller tables. There are some other thing you could check like setting the STATISTICS_IO to on or the SHOWPLAN to make the execution plan shippable to other peers with more information.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de