Login failed for user (null). Reason: Not associated with a trusted SQL

I am connecting to an Access 97 db on a network drive, in which all tables are linked to a SQL Server 2000 db through a DSN. I can access the tables fine from a Windows 2000 machine, but I get this error when I try to access the tables on an NT4 machine: Login failed for user '(null)'. Reason: Not associated with a trusted SQL. I do not want to use trusted security and the DSN does have a valid SQL Server user name and password. Please help!!!When you created the linked tables within the Access database you specify which DSN to use. That DSN must be defined on all machines that will use the linked tables within the Access database. Does the NT 4.0 workstation have the DSN defined on it? If so does it have trusted connection defined or Login/Password?|||I do have the dsn set up on both machines, but in further digging, I found this:

FIX: SQL Server ODBC Driver Ignores Authentication Setting (Q279526)

------------------------
The information in this article applies to:

Microsoft ODBC Driver for SQL Server, version 3.6
Microsoft SQL Server 2000 (all editions)
Microsoft Data Access Components version 2.6

------------------------

SYMPTOMS
When you use the SQL Server ODBC driver version 2000.080.0194, which was released with SQL Server 2000 and Microsoft Data Access Components (MDAC) 2.6 RTM, the authentication settings for ODBC data source names (DSNs) are ignored. The driver attempts to log directly into SQL Server using NTLM authentication (integrated security) without prompting for a user ID and password.

This can cause authentication failures, messages that database objects are not available, or unintentional modification of the wrong objects when copies of objects are maintained in multiple databases.

RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, please see the following article in the Microsoft Knowledge Base:

Logical Drive Letters

I am running a 3active/1passive node cluster on W2K3 and SQL 2k. The passive
node has the ability to have any of the active nodes to failover to it. In
addition to it being the failover node it also has 3 instances that match the
active nodes.
Since all the drive letters must be shared between the 6 instances I have
quickly run out of drive letters. Each node currently has 2 logical drives
accounting for 12 of the letters, add in local drives and cd drive,A-F and
Z:. I have 5 letters left.
I would like to add a seperate drive on each instance for the system dbs but
do not have enough letters left. Is there a way around this restriction?
Hi
No. Volumes without drive letters are not supported on Clusters.
Having a match of a DB to a drive letter does not gain you much, unless you
know each drive letter is a separate LUN and separate drives on the SAN.
We operate our SANS with 3 drivers per instance, a Data, a backup drive and
a log drive. All RAID-10. Each one is at SAN (EMC) level on different
drives.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Thom" <Thom@.discussions.microsoft.com> wrote in message
news:FC39CDC8-F010-4541-B0BB-6CE66DC45395@.microsoft.com...
>I am running a 3active/1passive node cluster on W2K3 and SQL 2k. The
>passive
> node has the ability to have any of the active nodes to failover to it.
> In
> addition to it being the failover node it also has 3 instances that match
> the
> active nodes.
> Since all the drive letters must be shared between the 6 instances I have
> quickly run out of drive letters. Each node currently has 2 logical drives
> accounting for 12 of the letters, add in local drives and cd drive,A-F and
> Z:. I have 5 letters left.
> I would like to add a seperate drive on each instance for the system dbs
> but
> do not have enough letters left. Is there a way around this restriction?
|||It sounds like you are mapping SQL 7.0 behavior to a SQL 2000 4-node
cluster. There are a lot of differences. First, each instance no longer
has a designated home node. You can limit the nodes an instance is allowed
to run on, but you are far better off allowing all nodes to be hosts for all
instances. You can move instances around on nodes as necessary. For
example, SQL_Instance_1 normally runs on Node A but can run on any node.
SQL2 and SQL3 normally run on nodes B and C respectively but also can run on
any other node. The second choice of all instances is node D, the normally
empty node. Once you have a failover (or just an instance move for
maintenance) you will need to rearrange the failover order to keep from
accidentally stacking the instances on the same node.
Each LUN should also map to a single drive letter cluster-wide. For
example, SQL_Instance_1 should use data drive R: and Log Drive S: on all
nodes. With three instances, you will have plenty of drive letters even with
the cluster overhead.
Geoff N. Hiten
Microsoft SQL Server MVP.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uBukmxNVFHA.3532@.TK2MSFTNGP09.phx.gbl...
> Hi
> No. Volumes without drive letters are not supported on Clusters.
> Having a match of a DB to a drive letter does not gain you much, unless
> you know each drive letter is a separate LUN and separate drives on the
> SAN.
> We operate our SANS with 3 drivers per instance, a Data, a backup drive
> and a log drive. All RAID-10. Each one is at SAN (EMC) level on different
> drives.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Thom" <Thom@.discussions.microsoft.com> wrote in message
> news:FC39CDC8-F010-4541-B0BB-6CE66DC45395@.microsoft.com...
>
|||Just to clarify I have 6 instances on a 4 node cluster. 3 of those instances
reside on one server most of the time while the other 3 are spread across the
other servers?
If drive letter A-F and Z are used for local drives on each of the nodes
that only leave 18 drives for the instances, Q is for quorum. At this point
I can only add 1 more drive letter to each instance or 6 drives total. Since
currently each instance has two drives. After I use these 6 drive letters
will there be any way to add additional drives to the instances.
I am wanting to keep my data spread out as much as possible to avoid Disk
I/O bottle necks.
"Thom" wrote:

> I am running a 3active/1passive node cluster on W2K3 and SQL 2k. The passive
> node has the ability to have any of the active nodes to failover to it. In
> addition to it being the failover node it also has 3 instances that match the
> active nodes.
> Since all the drive letters must be shared between the 6 instances I have
> quickly run out of drive letters. Each node currently has 2 logical drives
> accounting for 12 of the letters, add in local drives and cd drive,A-F and
> Z:. I have 5 letters left.
> I would like to add a seperate drive on each instance for the system dbs but
> do not have enough letters left. Is there a way around this restriction?
|||You are limited to only named drives a-z with SQL Server 2000. There is no
supported way around it. Can you consolidate some of your local drives to
make those letters availble for shared drives?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Logical Disk Fragmentation on Database Drive

We are using Disk Keeper Server from Executive Software version 7.0.410.0.
I am trying to minimize the logical fragmentation on the drive where our
database (.MDF) is located.
The problem I am having is that I do not have the drive space to move
the .MDF to another drive in order to defragment.
I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
then attempt to defrag without moving the file and this has not been
successful.
I thought I may be doing something wrong with Diskeeper or SQL 2000.
Any thoughts or ideas would be very helpful.
TIA,
-Ben
Ben wrote:
> We are using Disk Keeper Server from Executive Software version
> 7.0.410.0.
> I am trying to minimize the logical fragmentation on the drive where
> our database (.MDF) is located.
> The problem I am having is that I do not have the drive space to move
> the .MDF to another drive in order to defragment.
> I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
> then attempt to defrag without moving the file and this has not been
> successful.
> I thought I may be doing something wrong with Diskeeper or SQL 2000.
> Any thoughts or ideas would be very helpful.
> TIA,
> -Ben
Diskeeper requires a good amount of free drive space to best defrag
files. Since the MDF file you are defragging is large (I assume) and
there is little drive space left, Diskeeper appears to be having
trouble. How much free space do you have and how much space is there in
total? Do you know for a fact that the MDF file is heavily fragmented?
You could try shrinking the file using DBCC SHRINKFILE.
Run sp_spaceused on the database in question and see if there is
unallocated space. If so, shrink the file size, defrag, and then expand
the database again from SQL EM before returning the database to
production.
David G.

Logical Disk Fragmentation on Database Drive

We are using Disk Keeper Server from Executive Software version 7.0.410.0.
I am trying to minimize the logical fragmentation on the drive where our
database (.MDF) is located.
The problem I am having is that I do not have the drive space to move
the .MDF to another drive in order to defragment.
I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
then attempt to defrag without moving the file and this has not been
successful.
I thought I may be doing something wrong with Diskeeper or SQL 2000.
Any thoughts or ideas would be very helpful.
TIA,
-BenBen wrote:
> We are using Disk Keeper Server from Executive Software version
> 7.0.410.0.
> I am trying to minimize the logical fragmentation on the drive where
> our database (.MDF) is located.
> The problem I am having is that I do not have the drive space to move
> the .MDF to another drive in order to defragment.
> I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
> then attempt to defrag without moving the file and this has not been
> successful.
> I thought I may be doing something wrong with Diskeeper or SQL 2000.
> Any thoughts or ideas would be very helpful.
> TIA,
> -Ben
Diskeeper requires a good amount of free drive space to best defrag
files. Since the MDF file you are defragging is large (I assume) and
there is little drive space left, Diskeeper appears to be having
trouble. How much free space do you have and how much space is there in
total? Do you know for a fact that the MDF file is heavily fragmented?
You could try shrinking the file using DBCC SHRINKFILE.
Run sp_spaceused on the database in question and see if there is
unallocated space. If so, shrink the file size, defrag, and then expand
the database again from SQL EM before returning the database to
production.
David G.

Logical Disk Fragmentation on Database Drive

We are using Disk Keeper Server from Executive Software version 7.0.410.0.
I am trying to minimize the logical fragmentation on the drive where our
database (.MDF) is located.
The problem I am having is that I do not have the drive space to move
the .MDF to another drive in order to defragment.
I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
then attempt to defrag without moving the file and this has not been
successful.
I thought I may be doing something wrong with Diskeeper or SQL 2000.
Any thoughts or ideas would be very helpful.
TIA,
-BenBen wrote:
> We are using Disk Keeper Server from Executive Software version
> 7.0.410.0.
> I am trying to minimize the logical fragmentation on the drive where
> our database (.MDF) is located.
> The problem I am having is that I do not have the drive space to move
> the .MDF to another drive in order to defragment.
> I have tried to stop the MSSQLSERVER and SQLSERVERAGENT services and
> then attempt to defrag without moving the file and this has not been
> successful.
> I thought I may be doing something wrong with Diskeeper or SQL 2000.
> Any thoughts or ideas would be very helpful.
> TIA,
> -Ben
Diskeeper requires a good amount of free drive space to best defrag
files. Since the MDF file you are defragging is large (I assume) and
there is little drive space left, Diskeeper appears to be having
trouble. How much free space do you have and how much space is there in
total? Do you know for a fact that the MDF file is heavily fragmented?
You could try shrinking the file using DBCC SHRINKFILE.
Run sp_spaceused on the database in question and see if there is
unallocated space. If so, shrink the file size, defrag, and then expand
the database again from SQL EM before returning the database to
production.
David G.

Logic/Toggle Question

I am trying to do the following (without using a parameter box to drive the results)

I would like to be able to toggle the results instead of using a parameter.

The default view for the table data is any row that meets a threshold criteria (similar to a KPI)

I would then like for all of the data to be exposed when toggled which eliminates using IIF (unless I am missing something).

I would think that if I could reference the toggleState of a textbox I could do this (similar to a yes/no Show All parameter), but I found little to nothing on how to do this within Reporting Services.

I guess I could also use two datasets to achieve this, but I would prefer a more elegant result.

Are you looking for a kind of drill down?

If yes then a visibility condition can be written on the basis of threshhold criteria for the complete row of table and toggle item can be chosen (just below the hidden property).

So on the click of that texbox user would be able to toggle rows which are not crossing threshholds.

Hope this helps!

Priyank

|||

If I understand you correctly, not quite.

I would like the toggle button to show either the rows that meet the criteria or all rows.

Imagine you have 5 rows of data

1997 10

1998 12

1999 11

2000 9

2001 4

The threshold is < 8

The default view would be

2001 4

If you then hit the toggle button, I would like all records to be shown including the record meeting the threshold.

As I noted, I could achieve this with a parameter value or most likely through two datasets (overthreshold and underthreshold), but I was curious if you code obtain the toggle state of a textbox in embedded code. The ToggleState could act as an all or only threshold selection.