Authentification problem with SQL Server 2000

Hello !
We use SQL Server 2000 (standard edition) under Windows 2003 Server.
Due to a hardware failure, we have fully set up the server after having
formating the hard drives. After having installed Windows Server 2003, we
have installed SQL Server 2000, then we have restored the databases from our
last night SQL backup.
Curiously : all our Windows XP users can connect to the server, but not our
Windows 2000 users! We have tried to create an ODBC data source with Windows
authentication : failure. With SQL authentication : failure.
But the same user, with his same userid, on another PC under Windows XP : no
problem.
And it was working well before the crash. Can anybody give us an explanation
? a solution ? a help ?
Thank you,
GilbertDo you have TCP/IP enabled on the SQL Server as an allowed connection type?
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Hello !
> We use SQL Server 2000 (standard edition) under Windows 2003 Server.
> Due to a hardware failure, we have fully set up the server after having
> formating the hard drives. After having installed Windows Server 2003, we
> have installed SQL Server 2000, then we have restored the databases from
> our last night SQL backup.
> Curiously : all our Windows XP users can connect to the server, but not
> our Windows 2000 users! We have tried to create an ODBC data source with
> Windows authentication : failure. With SQL authentication : failure.
> But the same user, with his same userid, on another PC under Windows XP :
> no problem.
> And it was working well before the crash. Can anybody give us an
> explanation ? a solution ? a help ?
> Thank you,
> Gilbert
>|||Hi Warren,
Thank you for your answer. Could you tell us where to look at, to answer
your question ?
Gilbert
"Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
> Do you have TCP/IP enabled on the SQL Server as an allowed connection
> type?
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
> "Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
> news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
>|||http://technet.microsoft.com/en-us/...y/ms174212.aspx
You need to use the SQL Server configuration manager which has an option for
viewing which connections are allowed...
Its under your start menu programs in the same group as SQL Server...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
> Hi Warren,
> Thank you for your answer. Could you tell us where to look at, to answer
> your question ?
> Gilbert
> "Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
> news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
>|||Hi Warren,
Sorry to be a bit late, but : Thank you !
And a Happy New Year,
Gilbert
"Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
news: OJDKPu5QIHA.5288@.TK2MSFTNGP04.phx.gbl...
> http://technet.microsoft.com/en-us/...y/ms174212.aspx
> You need to use the SQL Server configuration manager which has an option
> for viewing which connections are allowed...
> Its under your start menu programs in the same group as SQL Server...
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
>
> "Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
> news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
>

Authentication/Security Issue!

Hi,
I have installed SQL reporting services on the local system test machine
[standard edition] which points to a DB that is on a different machine.
Everything works ok if I use a domain account and assign security rights for
each report. But in production I will want to have a local windows account
and assign read rights on the reports individually. I tried doing this in
the test environment.
When I try to access the site using the IP I get the windows log on box.
After entering the local user account I can get to the reports but as soon
as I try and run the report it gives me this error:
The permissions granted to user [domain\user] are insufficient for
performing this operation. (rsAccessDenied)
The problem is i am not logged on as a domain user but as a local machine
user.
Was wondering if any of you have come across this error before and possibly
know the cause/solution to this.
Thanks for your help!
Regards
AnilHi Anil:
Even if you go to an IP address for the server, when you run a report
the report is rendered by an IFRAME element with the URL pointing to
the report server by name.
To verify this behavior, just right-click in the report area, select
properties, and look at the URL. You'll notice your address bar might
look like http://x.x.x.x, but the report properties URL will indicate
http://reporting. The server always uses the <ReportServerUrl> element
in RSWebApplication.config.
Since the IFRAME points you back to the server by name, IE is probably
automatically logging you in again with your domain account, which is
not in a Browse role. You can change IE's behavior in Tools ->
Internet Options -> Security -> Custom Level -> User Authentication
(at the bottom of the list).
--
Scott
http://www.OdeToCode.com
On Mon, 16 Aug 2004 12:31:41 +1200, "anil" <test@.test.com> wrote:
>Hi,
>I have installed SQL reporting services on the local system test machine
>[standard edition] which points to a DB that is on a different machine.
>Everything works ok if I use a domain account and assign security rights for
>each report. But in production I will want to have a local windows account
>and assign read rights on the reports individually. I tried doing this in
>the test environment.
>When I try to access the site using the IP I get the windows log on box.
>After entering the local user account I can get to the reports but as soon
>as I try and run the report it gives me this error:
>
>The permissions granted to user [domain\user] are insufficient for
>performing this operation. (rsAccessDenied)
>The problem is i am not logged on as a domain user but as a local machine
>user.
>Was wondering if any of you have come across this error before and possibly
>know the cause/solution to this.
>Thanks for your help!
>Regards
>Anil
>

Authentication problem

2 Windows Server 2003 Standard Edtion Servers with Domain Controller, eg.: DC1 & DC2

4 Workstations (Win XP Pro SP2)

2 workstations are member of DC1, eg.: DC1_WS1 & DC1_WS2

and another 2 workstation are member of DC2, eg.: DC2_WS1 & DC2_WS2

SQL Server 2005 Express SP2 is installed on DC1_WS1 (Mix Authentication, Server Name: DC1)

My problem:

1. I use SSMSE on DC1_WS2, connect to DC1 with SQL Server Authentication (sa). Login Failed.

(I did off the firewall, enabled remote connections: Using both TCP/IP and named pipes)

My questions:

1. with the above setup, is it possible to use DC2_WS1 connect to DC1?

2. is my problem will be solved if I install SQL Server 2005 Exprees in DC1?

Please advise. Thanks.

1) You should be able to connect with SQL Authentication. What's your exact error message? What did you see in the server errorlog?

2) Install SQL Server on DC is not recommended.

|||

"2) Install SQL Server on DC is not recommended. "

This means SQL Server is better install on workstation?

|||Yes. Just don't share a machine with DC, otherwise, it may cause configuration issue hard to track.

Auth.

what if we are making the ASP(Application Service provider) model so we have
to go for windows authentication or standard authentication?
Can you be more elaborate on what your question is?
You can use either of the mechanism as authentication models. But what is
your requirement?
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"Rogers" <Rogers@.discussions.microsoft.com> wrote in message
news:F11D42D4-EA39-4E22-A390-DB7A933FD91B@.microsoft.com...
> what if we are making the ASP(Application Service provider) model so we
have
> to go for windows authentication or standard authentication?
|||at what point we have to go for windows authentication and at what point we
have to consider to go for standard authentication means through database
user.
"Vinod Kumar" wrote:

> Can you be more elaborate on what your question is?
> You can use either of the mechanism as authentication models. But what is
> your requirement?
> --
> HTH,
> Vinod Kumar
> MCSE, DBA, MCAD, MCSD
> http://www.extremeexperts.com
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinf...2000/books.asp
> "Rogers" <Rogers@.discussions.microsoft.com> wrote in message
> news:F11D42D4-EA39-4E22-A390-DB7A933FD91B@.microsoft.com...
> have
>
>

auditing the table

Hi,
I would like to audit table but I do not want to use
profiler. I need to know NT user name not just sql server
standard login for the user. The problem is that somebody
ocasssionally deletes the data and I would like to find
out who is doing it.
Any view is appreciated.You could create a TRIGGER on the table. eg :-
CREATE TRIGGER reminder
ON titles
FOR DELETE
AS
EXEC master..xp_sendmail 'ToYou',
'Someone just deleted a row'
GO
this could easily be enhanced to log to a table, you can capture the user
name of who did the deletion by capturing USER_NAME
HTH
Ryan Waight, MCDBA, MCSE
"Mirna" <mstojsic@.hotmail.com> wrote in message
news:2739901c38f3d$83e5d340$a601280a@.phx.gbl...
> Hi,
> I would like to audit table but I do not want to use
> profiler. I need to know NT user name not just sql server
> standard login for the user. The problem is that somebody
> ocasssionally deletes the data and I would like to find
> out who is doing it.
> Any view is appreciated.
>

Attribute Limit of 5000 When Mining a Cube

I'm trying to build a association model in the Standard Edition based on an existing cube. I keep getting the error:

Error (Data mining): The 'Product Recommendations' mining model has 60385 attributes. This number of attributes exceeds the attribute limit of 5000 allowed by the current version of the algorithm associated with the mining model.

I created Cube Slice filters and those limit the Customer and Product dimensions (Product is Nested) to well under 5000. The error message also does not change. The number of attributes is equal to the number of rows in the Product dimension, but I expected the cube slice to reduce the number. I tested all the SQL used while it processes and with the MDXFilters the number of rows returned is well under 5000.

So, in short, the final questions is, is it possible to create a mining model in standard edition based on an existing cube where the nested dimension in the model has more than 5000 rows? Is there some other way to filter the query?

I guess my only choice on this if there isn't a way is to extract the data into relational table with only the rows I want to analyze....that's a huge pain and doesn't really make sense when the filters should limit the model size.

What is annoying on this is I can't find one reference anywhere on the microsoft site that this limit even exists within the product...

Thanks for any assistance on this!

This sounds like a bug (and knowing the code, I can see where it comes from).

Standard edition is limited to 5000 attributes for Standard Edition. What you are doing is perfectly legal, assuming there are actually less than 5000 attributes. You may need to contact support so we can get this fixed, or start by writing up a bug report at connect.microsoft.com. If you cannot get this resolved through support and this is blocking you, please let us know and we will see if we can make something happen.

Thanks

-Jamie

|||

Thanks...I'll get a support case open and see what happens.

- L

|||

Jamie,

I opened a support case with Microsoft and have been working with them for a few days. They did agree that this is a defect in the product. The current response is that, "they may consider a design change to account for filtered cube slices". This is a pretty big deal for our development. I'd also question the limit in general since its not even documented, does the limit really drive more sales to the Enterprise Version of the product? I think if there is a limit, it should really be much larger since in practice, 5000 rows in a nested table is so small. It is very common for small companies to have product catalogs of 60k products.

THANKS!

|||

I have been working with the support person you are in contact with. The issue isn't if the problem with be fixed, it is simply how the problem will be fixed. I believe we will have a resolution today - in any case, it will resolve the issue you are seeing.

Regarding the 5000 attribute limit, that's a completely seperate debate that I don't want to get deeply into in the forums. I would only state that the differentiation between the various editions isn't limited to data volumes, functional differences arise as well (e.g. data mining transforms in Integration Services, etc.). Your cost structure in general may not support a wholesale changeover to Enterprise edition due to data volumes, but the ROI of some of the features that are made available in the larger edition may warrant an upgrade on a single machine. There are different licensing options for this as well, i.e. server CAL vs Processor licences, which for a small-medium size business, a 50-CAL Enterprise license may do the trick and still be in the affordable price range.

If you want to contact me directly, it's Jamie <dot> MacLennan <at> microsoft <dot> com

Thanks

Attribute Limit of 5000 When Mining a Cube

I'm trying to build a association model in the Standard Edition based on an existing cube. I keep getting the error:

Error (Data mining): The 'Product Recommendations' mining model has 60385 attributes. This number of attributes exceeds the attribute limit of 5000 allowed by the current version of the algorithm associated with the mining model.

I created Cube Slice filters and those limit the Customer and Product dimensions (Product is Nested) to well under 5000. The error message also does not change. The number of attributes is equal to the number of rows in the Product dimension, but I expected the cube slice to reduce the number. I tested all the SQL used while it processes and with the MDXFilters the number of rows returned is well under 5000.

So, in short, the final questions is, is it possible to create a mining model in standard edition based on an existing cube where the nested dimension in the model has more than 5000 rows? Is there some other way to filter the query?

I guess my only choice on this if there isn't a way is to extract the data into relational table with only the rows I want to analyze....that's a huge pain and doesn't really make sense when the filters should limit the model size.

What is annoying on this is I can't find one reference anywhere on the microsoft site that this limit even exists within the product...

Thanks for any assistance on this!

This sounds like a bug (and knowing the code, I can see where it comes from).

Standard edition is limited to 5000 attributes for Standard Edition. What you are doing is perfectly legal, assuming there are actually less than 5000 attributes. You may need to contact support so we can get this fixed, or start by writing up a bug report at connect.microsoft.com. If you cannot get this resolved through support and this is blocking you, please let us know and we will see if we can make something happen.

Thanks

-Jamie

|||

Thanks...I'll get a support case open and see what happens.

- L

|||

Jamie,

I opened a support case with Microsoft and have been working with them for a few days. They did agree that this is a defect in the product. The current response is that, "they may consider a design change to account for filtered cube slices". This is a pretty big deal for our development. I'd also question the limit in general since its not even documented, does the limit really drive more sales to the Enterprise Version of the product? I think if there is a limit, it should really be much larger since in practice, 5000 rows in a nested table is so small. It is very common for small companies to have product catalogs of 60k products.

THANKS!

|||

I have been working with the support person you are in contact with. The issue isn't if the problem with be fixed, it is simply how the problem will be fixed. I believe we will have a resolution today - in any case, it will resolve the issue you are seeing.

Regarding the 5000 attribute limit, that's a completely seperate debate that I don't want to get deeply into in the forums. I would only state that the differentiation between the various editions isn't limited to data volumes, functional differences arise as well (e.g. data mining transforms in Integration Services, etc.). Your cost structure in general may not support a wholesale changeover to Enterprise edition due to data volumes, but the ROI of some of the features that are made available in the larger edition may warrant an upgrade on a single machine. There are different licensing options for this as well, i.e. server CAL vs Processor licences, which for a small-medium size business, a 50-CAL Enterprise license may do the trick and still be in the affordable price range.

If you want to contact me directly, it's Jamie <dot> MacLennan <at> microsoft <dot> com

Thanks

Attaching a SQL Express database to SQL Server Standard instance...

If I create a database in SQL Express and then copy the MDF/LDF files and attach them to a machine running SQL Server 2005 Standard - will this new database have SQL Express limitations?

Are there good reasons not to do this and create the database in SQL Server Standard using scripts generated from the SQL Express instance instead?

Basically, I'm setting up a merge replication between Standard and SQL Express for a common database and I figure attaching a copy of the database created in SQL Express is the fastest way to get this started.

Moving this thread over to the Express forum. They may be able to help with the limitations question.

Thanks,
Sam

|||

You can attach the file created on SQL Express to SQL Standard Edition, they are the same product and use the same file format. The limitation are specific to SQL Express, not the database file itself. In comparing copying the file and running a scirpt, I'm not aware of any particular benefits or limitations of one over the other.

From the stand point of Replication, there is no particular reason you need to do it this way. I'm guessing that you are developing locally using SQL Express and then moving your database to SQL Standard to setup your Publication. To my knowledge (I'm not a repl expert) you don't actually need to have a copy of the database on SQL Express in order to create a Subscription once you set up your Publisher on Standard. I believe you can configure things so that a database is created at the Subscriber when you initialize a new Subscription. That's obviously a question for the Repl forum if you run into issues there.

Mike