Dataset error when deployed to Report Manager

Hi
I've got a custom assembly which performs validation on parameters
prior to submitting the query to the database. My dataset which
retrieves the report data is in Text format and calls an appropriate
validation method on free-text parameters, such as dates and numbers.
When validation passes, the code returns a string formatted for use in
the query, and when it fails it returns a string value that the stored
procedure recognises as a dummy value and returns without SELECTing any
data. My custom assembly sets a user-friendly error message as a
property, which is displayed on the report in place of any data.
I've designed a number of reports using this method and it works well
in the Designer environment. However, I've deployed a few of them to
Report Manager and am getting the following error when pressing "View
Report":
An error has occurred during report processing. (rsProcessingAborted)
Cannot set the command text for data set 'Report'.
(rsErrorSettingCommandText)
Error during processing of the CommandText expression of dataset
'Report'. (rsQueryCommandTextProcessingError)
An example of one of the simple Datasets is:
="EXEC spAgentSettlementsDetailedRpt " &
Code.Validator.ResetValidator &
"@.p_StartDate_IN = '" +
Code.Validator.ValidateStartDate(Parameters!p_StartDate_IN.Value) + "',
" &
"@.p_EndDate_IN= '" +
Code.Validator.ValidateEndDate(Parameters!p_StartDate_IN.Value,
Parameters!p_EndDate_IN.Value) + "', " &
"@.p_AgentID_IN = " + Parameters!p_AgentID_IN.Value.ToString() + ", "
&
"@.p_WS_Code_IN = " +
Code.Validator.ValidateWSCode(Parameters!p_WS_Code_IN.Value,
Parameters!p_AgentID_IN.Value, false)
I'm happy to provide the code within the assembly if it would be of any
help in debugging this problem.
In deploying to the server, I have copied the assembly (dll) to the
\bin directory on the server and uploaded the rdl file as per normal.
Any help would be greatly appreciated. Thank you.
AshleyI've discovered what was causing the error... it turned out to be a
security/permissions problem. The validate date methods attempted to
set the culture of the current thread to "en-AU" with the following
statement:
Thread.CurrentThread.CurrentCulture = New CultureInfo("en-AU")
This was to get around the fact that the result of the VB IsDate()
function appears to be dependent upon the culture settings of the
server. It was always returning false for dd/mm/yyyy dates such as
13/1/2005.
The above line of code was causing an exception to be raised in the
assembly and hence was returning garbage to the dataset.
Does anyone know the precise reason that setting the culture of the
thread, once the report is deployed, results in an exception?
Ashley.Manos@.gmail.com wrote:
> Hi
> I've got a custom assembly which performs validation on parameters
> prior to submitting the query to the database. My dataset which
> retrieves the report data is in Text format and calls an appropriate
> validation method on free-text parameters, such as dates and numbers.
> When validation passes, the code returns a string formatted for use in
> the query, and when it fails it returns a string value that the stored
> procedure recognises as a dummy value and returns without SELECTing any
> data. My custom assembly sets a user-friendly error message as a
> property, which is displayed on the report in place of any data.
> I've designed a number of reports using this method and it works well
> in the Designer environment. However, I've deployed a few of them to
> Report Manager and am getting the following error when pressing "View
> Report":
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot set the command text for data set 'Report'.
> (rsErrorSettingCommandText)
> Error during processing of the CommandText expression of dataset
> 'Report'. (rsQueryCommandTextProcessingError)
> An example of one of the simple Datasets is:
> ="EXEC spAgentSettlementsDetailedRpt " &
> Code.Validator.ResetValidator &
> "@.p_StartDate_IN = '" +
> Code.Validator.ValidateStartDate(Parameters!p_StartDate_IN.Value) + "',
> " &
> "@.p_EndDate_IN= '" +
> Code.Validator.ValidateEndDate(Parameters!p_StartDate_IN.Value,
> Parameters!p_EndDate_IN.Value) + "', " &
> "@.p_AgentID_IN = " + Parameters!p_AgentID_IN.Value.ToString() + ", "
> &
> "@.p_WS_Code_IN = " +
> Code.Validator.ValidateWSCode(Parameters!p_WS_Code_IN.Value,
> Parameters!p_AgentID_IN.Value, false)
> I'm happy to provide the code within the assembly if it would be of any
> help in debugging this problem.
> In deploying to the server, I have copied the assembly (dll) to the
> \bin directory on the server and uploaded the rdl file as per normal.
> Any help would be greatly appreciated. Thank you.
> Ashley|||I've discovered what was causing the error... it turned out to be a
security/permissions problem. The validate date methods attempted to
set the culture of the current thread to "en-AU" with the following
statement:
Thread.CurrentThread.CurrentCulture = New CultureInfo("en-AU")
This was to get around the fact that the result of the VB IsDate()
function appears to be dependent upon the culture settings of the
server. It was always returning false for dd/mm/yyyy dates such as
13/1/2005.
The above line of code was causing an exception to be raised in the
assembly and hence was returning garbage to the dataset.
Does anyone know the precise reason that setting the culture of the
thread, once the report is deployed, results in an exception?
> Hi
> I've got a custom assembly which performs validation on parameters
> prior to submitting the query to the database. My dataset which
> retrieves the report data is in Text format and calls an appropriate
> validation method on free-text parameters, such as dates and numbers.
> When validation passes, the code returns a string formatted for use in
> the query, and when it fails it returns a string value that the stored
> procedure recognises as a dummy value and returns without SELECTing any
> data. My custom assembly sets a user-friendly error message as a
> property, which is displayed on the report in place of any data.
> I've designed a number of reports using this method and it works well
> in the Designer environment. However, I've deployed a few of them to
> Report Manager and am getting the following error when pressing "View
> Report":
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot set the command text for data set 'Report'.
> (rsErrorSettingCommandText)
> Error during processing of the CommandText expression of dataset
> 'Report'. (rsQueryCommandTextProcessingError)
> An example of one of the simple Datasets is:
> ="EXEC spAgentSettlementsDetailedRpt " &
> Code.Validator.ResetValidator &
> "@.p_StartDate_IN = '" +
> Code.Validator.ValidateStartDate(Parameters!p_StartDate_IN.Value) + "',
> " &
> "@.p_EndDate_IN= '" +
> Code.Validator.ValidateEndDate(Parameters!p_StartDate_IN.Value,
> Parameters!p_EndDate_IN.Value) + "', " &
> "@.p_AgentID_IN = " + Parameters!p_AgentID_IN.Value.ToString() + ", "
> &
> "@.p_WS_Code_IN = " +
> Code.Validator.ValidateWSCode(Parameters!p_WS_Code_IN.Value,
> Parameters!p_AgentID_IN.Value, false)
> I'm happy to provide the code within the assembly if it would be of any
> help in debugging this problem.
> In deploying to the server, I have copied the assembly (dll) to the
> \bin directory on the server and uploaded the rdl file as per normal.
> Any help would be greatly appreciated. Thank you.
> Ashley

DataReader Source can not configurate

when I configurate the datareader source using the ODBC connection manager. it show the follow error message:
"Error at Data Flow Task[DataReader Source [562]]: Cannot acquire a managed connection from the run-time connection manager"
this ODBC is connect to IBM DB2.

Can anyone help on this?

Frank,

see this thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=379235&SiteID=1

Thanks.

DataReader output column length

Hello,

I have an ODBC connection manager to a Progress database. In that database there is a column declared as a string of 10 characters long.
However, some data in this column is actually up to 15 characters long.
This makes my DataReader Source fail everytime I try to run my package because it sets the output column like this :

Datatype : Unicode string [DT_WSTR]
Length : 10

Is there any way to solve this without changing the datatype in the Progress database (that is beyond my control) ?

tanks in advance ...

What are you talking about? How can you have a column declared with a width of 10 and have data that exceeds that length? You might want to double check your source metadata.|||

renyx wrote:

In that database there is a column declared as a string of 10 characters long.
However, some data in this column is actually up to 15 characters long.

That is a physical impossibility.

Can you expand more on what you mean?

-Jamie

|||

In Progress a column can be declared as Char(10) while creating the table, but while inserting in the table, a value larger than 10 can be inserted without causing an error.

So I am looking for a way to make the DataReader output column 15 in length.

|||

renyx wrote:

In Progress a column can be declared as Char(10) while creating the table, but while inserting in the table, a value larger than 10 can be inserted without causing an error.

So I am looking for a way to make the DataReader output column 15 in length.

Really? OK, I take it back. Sorry. That's just....bizarre....for want of a better word.

I think you'll be able to go into the Advanced Editor of the Datareader Source and manually edit the column lengths.

|||

Jamie Thomson wrote:

Really? OK, I take it back. Sorry. That's just....bizarre....for want of a better word.

I think you'll be able to go into the Advanced Editor of the Datareader Source and manually edit the column lengths.

I just looked into this some... Progress 4GL does not use the width definition for the storage of data. Character data types in Progress 4GL can be up to 2,000 characters, I believe. The char(10) definition that the OP mentioned is for query results, I believe, and not for storage.

So, how to get around this? Well, do as Jamie suggested and edit the Datareader Source manually using the advanced editor.|||

Thanks for the suggestion, but that did not work.
I also tried a query on the column in management studio (linked server) and that also did not work.

OLE DB provider "MSDASQL" for linked server "LISA" returned message "[DataDirect][ODBC OPENEDGE driver][OPENEDGE]Column KM4-CODE in table PUB.ARTIKEL has value exceeding its max length or precision.".

Looks like I will have to convince the Progress people to change the datatype.

|||This is a well known Progress problem. Check out http://www.progresstalk.com/archive/index.php?t-76301.html|||By the way, I'm just going on record to say that the Progress leaders should be sent back to logic school for designing a product that enforces the data length on a one-way basis. "Um yeah, we let you store data greater than what's defined, but we won't let you select it back out."

That's the most ridiculous thing I have heard in a long time.|||Same issue happens to me. We import data from a Thoroughbred basic database. The field can be 12 chars long with 20 chars of data. In the Thoroughbred world, this is just an "integrity" problem....Their db still works somehow, but causes fits on our end.|||

If anyone out there wants a humorous outlook on this (and promises not to take offence to SQL zealots), go here: http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=263&messageid=340643

-Jamie

|||

Thoroughbred still lives? Aaargh! The only implementation of a computer language I ever saw that allowed indefinite GOTOs (I'm not kidding). I had not heard about this "integrity" issue with their DB, but am not surprised.

|||

renyx wrote:

Thanks for the suggestion, but that did not work.
I also tried a query on the column in management studio (linked server) and that also did not work.

OLE DB provider "MSDASQL" for linked server "LISA" returned message "[DataDirect][ODBC OPENEDGE driver][OPENEDGE]Column KM4-CODE in table PUB.ARTIKEL has value exceeding its max length or precision.".

Looks like I will have to convince the Progress people to change the datatype.

Renyx, did you try changing the SqlCommand select statement to cast the column to something longer?
As you noted, you cannot change the column length in the advanced editor, but doing so in the select statement might work for you.

Dataflow Tab:There is no ODBC Source option in the Toolbox

I need to extract data from tables in a database that I can only access via ODBC.

I have successfully created a connection in Connection Manager (ConnectionManagerType = ODBC) for this database.

However I’m unable to add this connection as a Data Flow Source. There is no ODBC Source option in the Toolbox.

This is a major because we have been using the system dsn Microsoft Visual Foxpro Driver to access free table directory .dbf files under ODBC with DTS for years. To install a new Microsoft OLEDB driver for foxpro is out of the question on a production system as it would cost many thousands of dollars to go through our BAT testing process

How do I extract data from tables in a database via ODBC?

Thanks in advance

Dave

There is too, though it's not marked as such. Use the Data Reader Source.|||

You can use the script component as source.

|||

Thanks for that the data reader souce can actually use a ODBC source. I have it working fine.

I do think there is a peformance overhead and its slower than the ODBC connector in DTS.

|||

well that is interesting How can it connect to a foxpro file .dbf and matching .fpt file the .fpt files are used for memo text fieldsthe foxprpro ODBC driver does this for you behind the scenes

|||

Vijay Thirugnanam wrote:

You can use the script component as source.

True, though it shouldn't be faster than using the prepackaged source connectors.

Data-driven subscriptions - SQLRS Ent vs Std

I want to use data-driven subscriptions but cannot create one - the "New
data-driven subscription" button does not appear in Report manager. I
believe this may be because I'm running SQLRS Standard - can someone confirm
this please?
If true, is there an easy way to upgrade to SQLRS Enterprise or do I have to
uninstall Std and do a fresh install of Enterprise? Is there a way to save
and restore all my subscriptions?
thanks
PeterThe data Driven Subscriptions are only part of the enterprise version. I
don't think you have to uninstall to put in the entprise license. It won't
affect your subscriptions.
Stuart
"PeterB" wrote:
> I want to use data-driven subscriptions but cannot create one - the "New
> data-driven subscription" button does not appear in Report manager. I
> believe this may be because I'm running SQLRS Standard - can someone confirm
> this please?
> If true, is there an easy way to upgrade to SQLRS Enterprise or do I have to
> uninstall Std and do a fresh install of Enterprise? Is there a way to save
> and restore all my subscriptions?
> thanks
> Peter|||From Microsoft Website
Evaluation, Developer, or Enterprise Edition of SQL Server 2005. Support for data-driven subscriptions is not available in Standard, Workgroup, or SQL Server Express Editions. For more information, see Features Supported by the Editions of SQL Server 2005.
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Data-driven subscription not working

I created a data-driven subscription for my report with "Null Delivery Provider" set in report manager. I set the processing to "On a schedule created for this subscription" and scheduled the report to "run once" in the next 1 minute so I could test it. The subscription added successfully, but I don't see the "last run information" even after 5 minutes. Am I missing something?

Thanks in advance!!!

Check SQL Server for any failures reported in the log.

Data-Driven Subscription not shown

I am upgradinding to sql 2005 and the Data-Driven subscription is not working. the data-Driven option It is now showing in report manager and in code I get the error " rsOperationisNotSupported".... I have the same security permitions I had before in sql 2000. Does anyone knows if there is another difference that would prevent the subscription from working ?

thank you

drey

What sku of SQL 2005 are you using? Data driven subscriptions are only supported on developer and enterprise editions.|||

thank you,

I am using Standard edition, my company does not have enterprise. I guess that is a deal breaker for upgrading...

|||

Data driven subscriptions was also an Enterprise / Developer Edition in RS 2000. It was not available for the Standard Edition.

-- Robert

Data-Driven Subscription not appearing

Hi All,
When I click on a report in report manager, and go to subscriptions only a
Normal Subscription Oprion appears.
The Data-Driven Subscription does not appear.
Is there an otion to make this visible somewhere.?
Thanks
SanjeevData Driven Subscriptions are only available for the Enterprise Sku. Do you
have enterprise?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sanjeev" <sanjeev@.microsoft.com> wrote in message
news:%23u7wLD09FHA.3928@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> When I click on a report in report manager, and go to subscriptions only a
> Normal Subscription Oprion appears.
> The Data-Driven Subscription does not appear.
> Is there an otion to make this visible somewhere.?
> Thanks
> Sanjeev
>|||Yes I do have Enterprise Sku.
We are planning to install SQL Server 2005 at some stage as well.
Does data driven subscriptions only come with the enterprise edition of this
as well?
Thanks for your assistance
Sanjeev
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:uEjA5Nq%23FHA.3852@.TK2MSFTNGP14.phx.gbl...
> Data Driven Subscriptions are only available for the Enterprise Sku. Do
> you have enterprise?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Sanjeev" <sanjeev@.microsoft.com> wrote in message
> news:%23u7wLD09FHA.3928@.TK2MSFTNGP11.phx.gbl...
>> Hi All,
>> When I click on a report in report manager, and go to subscriptions only
>> a Normal Subscription Oprion appears.
>> The Data-Driven Subscription does not appear.
>> Is there an otion to make this visible somewhere.?
>> Thanks
>> Sanjeev
>|||Yes it does.
The Data Driven button will also not show up if you do not have permission
to create DD subscriptions for that report. Make sure you have Manage All
Subscription permission.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sanjeev" <sanjeev@.microsoft.com> wrote in message
news:%23NP0WT$%23FHA.912@.TK2MSFTNGP11.phx.gbl...
> Yes I do have Enterprise Sku.
> We are planning to install SQL Server 2005 at some stage as well.
> Does data driven subscriptions only come with the enterprise edition of
> this as well?
> Thanks for your assistance
> Sanjeev
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:uEjA5Nq%23FHA.3852@.TK2MSFTNGP14.phx.gbl...
>> Data Driven Subscriptions are only available for the Enterprise Sku. Do
>> you have enterprise?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Sanjeev" <sanjeev@.microsoft.com> wrote in message
>> news:%23u7wLD09FHA.3928@.TK2MSFTNGP11.phx.gbl...
>> Hi All,
>> When I click on a report in report manager, and go to subscriptions only
>> a Normal Subscription Oprion appears.
>> The Data-Driven Subscription does not appear.
>> Is there an otion to make this visible somewhere.?
>> Thanks
>> Sanjeev
>>
>|||Sorry, I misinterpreted you, we actually do not have Enterprise sku
installed at our site where I was trying to create DD subscriptions.
Unfortunately, we need to send reports, which takes the recipient's name as
a parameter, to about 500 recipients.
DD Subscriptions would have been ideal.
I do not think this is feasible to create 500 subscriptions for each report
using the normal subscription way.
Thanks for all your help
Sanjeev
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:ea1jIDC$FHA.3136@.TK2MSFTNGP15.phx.gbl...
> Yes it does.
> The Data Driven button will also not show up if you do not have permission
> to create DD subscriptions for that report. Make sure you have Manage All
> Subscription permission.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Sanjeev" <sanjeev@.microsoft.com> wrote in message
> news:%23NP0WT$%23FHA.912@.TK2MSFTNGP11.phx.gbl...
>> Yes I do have Enterprise Sku.
>> We are planning to install SQL Server 2005 at some stage as well.
>> Does data driven subscriptions only come with the enterprise edition of
>> this as well?
>> Thanks for your assistance
>> Sanjeev
>> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> news:uEjA5Nq%23FHA.3852@.TK2MSFTNGP14.phx.gbl...
>> Data Driven Subscriptions are only available for the Enterprise Sku. Do
>> you have enterprise?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Sanjeev" <sanjeev@.microsoft.com> wrote in message
>> news:%23u7wLD09FHA.3928@.TK2MSFTNGP11.phx.gbl...
>> Hi All,
>> When I click on a report in report manager, and go to subscriptions
>> only a Normal Subscription Oprion appears.
>> The Data-Driven Subscription does not appear.
>> Is there an otion to make this visible somewhere.?
>> Thanks
>> Sanjeev
>>
>>
>

databse properties causes mmc to close

Please help,
I am running SQL Server 2000 on a Windows 2000 server.
Whenever I open the Enterprise Manager and I right-click on any database and
select properties, the entire console just closes. No error or alert is cre
ated.
What should I doHave a look at Event log and see if there's anything there. Also, be sure to
update your sqlserver with latest service pack (sp3a).
-oj
http://www.rac4sql.net
"john" <anonymous@.discussions.microsoft.com> wrote in message
news:4BEAD47A-C47B-47ED-83EA-6AC9E00BE098@.microsoft.com...
> Please help,
> I am running SQL Server 2000 on a Windows 2000 server.
> Whenever I open the Enterprise Manager and I right-click on any database
and select properties, the entire console just closes. No error or alert is
created.
> What should I do|||I have SP3 loaded and I've checked the event logs but there is nothing regar
ding SQL.

Databases not showing up in EM on sql 2000, but do in 2005.

We have a SQL 2000 server that started showing 'no items' in enterprise
manager. However, when you connect with SQL2005 client tools they show up.
Any ideas?Eric
Have you "Refresh" on database folder?
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:0AE0271E-33B9-4225-B007-A8D023103627@.microsoft.com...
> We have a SQL 2000 server that started showing 'no items' in enterprise
> manager. However, when you connect with SQL2005 client tools they show up.
> Any ideas?

Databases not displayed in Enterprise manager

Hi
I'm experiencing a weird problem, I have a sql server running with lots of d
ifferent database and corresponding user to each database. Now the problem i
s that when a given user connects through EM the database in in EM list "no
items" for all users except
one, and the sa. Now I have just reinstalled the server, thought it was a pr
oblem in the software, attached the databases and added the users all the sa
me way, no special settings except for the assign of access as dbo to their
own database.
Even creating a new database, and adding a new user results in the same stuf
f....
On my local development machine, doing the exact same thing dowsn't result i
n the mentioned behavoir.
WHY? (the desparate dba)Found that everytime a user who cannot acces databases connects this shows u
p in the server log:
SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEP
TION_ACCESS_VIOLATION. SQL Server is terminating this process..
****************************************
************************************
***
*
* BEGIN STACK DUMP:
* 04/16/04 22:38:12 spid 56
*
* Exception Address = 00402453 (RecBase::Resize(void) + 00000004 Line 0+00
000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
* Input Buffer 68 bytes -
* exec sp_MSdbuseraccess N'db', N'%'
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B19FFF 0071a000
* ntdll 77F80000 77FFCFFF 0007d000
* KERNEL32 7C570000 7C627FFF 000b8000
* ADVAPI32 7C2D0000 7C331FFF 00062000
* RPCRT4 77D30000 77DA0FFF 00071000
* USER32 77E10000 77E74FFF 00065000
* GDI32 77F40000 77F7DFFF 0003e000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 78000000 78044FFF 00045000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 780A0000 780B1FFF 00012000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 7B470000 7B4BEFFF 0004f000
* SECUR32 7C340000 7C34EFFF 0000f000
* NETRAP 7B4C0000 7B4C5FFF 00006000
* SAMLIB 7B4D0000 7B4DEFFF 0000f000
* WS2_32 7B4E0000 7B4F3FFF 00014000
* WS2HELP 7B500000 7B507FFF 00008000
* WLDAP32 7B510000 7B539FFF 0002a000
* DNSAPI 7B540000 7B563FFF 00024000
* WSOCK32 7B570000 7B577FFF 00008000
* wmi 7B760000 7B763FFF 00004000
* ole32 7B870000 7B95EFFF 000ef000
* XOLEHLP 7B9E0000 7B9E7FFF 00008000
* MSDTCPRX 7B9F0000 7BAA6FFF 000b7000
* MTXCLU 7BAB0000 7BABFFFF 00010000
* VERSION 7BAC0000 7BAC6FFF 00007000
* LZ32 7BAD0000 7BAD5FFF 00006000
* CLUSAPI 7BAE0000 7BAEFFFF 00010000
* RESUTILS 7BAF0000 7BAFCFFF 0000d000
* USERENV 7C0F0000 7C150FFF 00061000
* rnr20 7BB00000 7BB0BFFF 0000c000
* iphlpapi 7BB50000 7BB62FFF 00013000
* ICMP 7BB70000 7BB74FFF 00005000
* MPRAPI 7BB80000 7BB96FFF 00017000
* OLEAUT32 7BBA0000 7BC3AFFF 0009b000
* ACTIVEDS 7BC40000 7BC6EFFF 0002f000
* ADSLDPC 7BC70000 7BC92FFF 00023000
* RTUTILS 7BCA0000 7BCADFFF 0000e000
* SETUPAPI 7BCB0000 7BD3DFFF 0008e000
* RASAPI32 7BD40000 7BD72FFF 00033000
* RASMAN 7BD80000 7BD90FFF 00011000
* TAPI32 7BDA0000 7BDC1FFF 00022000
* COMCTL32 7BDD0000 7BE53FFF 00084000
* SHLWAPI 7BE60000 7BEC4FFF 00065000
* DHCPCSVC 7BED0000 7BEE8FFF 00019000
* winrnr 011F0000 011F7FFF 00008000
* rasadhlp 01200000 01204FFF 00005000
* SSNETLIB 019D0000 019E5FFF 00016000
* SSNMPN70 410D0000 410D5FFF 00006000
* security 01CD0000 01CD3FFF 00004000
* crypt32 7C740000 7C7C6FFF 00087000
* MSASN1 01CE0000 01CEFFFF 00010000
* msafd 02100000 0211DFFF 0001e000
* wshtcpip 02160000 02166FFF 00007000
* SSmsLPCn 021F0000 021F6FFF 00007000
* ntdsapi 02290000 022A0FFF 00011000
* SQLFTQRY 02810000 0282CFFF 0001d000
* CLBCATQ 02830000 028BFFFF 00090000
* sqloledb 028E0000 02952FFF 00073000
* MSDART 02960000 0297EFFF 0001f000
* comdlg32 02980000 029BDFFF 0003e000
* SHELL32 029C0000 02C07FFF 00248000
* MSDATL3 02C10000 02C24FFF 00015000
* oledb32 02FB0000 03015FFF 00066000
* OLEDB32R 03020000 0302FFFF 00010000
* msv1_0 03050000 03070FFF 00021000
* xpstar 410F0000 41133FFF 00044000
* SQLUNIRL 10000000 1002CFFF 0002d000
* WINSPOOL 03080000 0309DFFF 0001e000
* MPR 030A0000 030AFFFF 00010000
* SQLRESLD 42AC0000 42AC6FFF 00007000
* SQLSVC 030B0000 030C6FFF 00017000
* ODBC32 030D0000 03101FFF 00032000
* odbcbcp 03110000 03115FFF 00006000
* W95SCM 41140000 4114BFFF 0000c000
* NDDEAPI 03120000 03126FFF 00007000
* odbcint 03270000 03285FFF 00016000
* SQLSVC 03290000 03295FFF 00006000
* xpstar 032A0000 032ABFFF 0000c000
* srchadm 034E0000 0351DFFF 0003e000
* mssadmws 03520000 03534FFF 00015000
* msi 03820000 03A23FFF 00204000
* athprxy 03A40000 03A47FFF 00008000
* rsabase 7CA00000 7CA22FFF 00023000
* xpsqlbot 04160000 04165FFF 00006000
* DBGHELP 042B0000 042C2FFF 00013000
* msdbi 04AF0000 04B0BFFF 0001c000
* sqlimage 09D20000 09D2CFFF 0000d000
*
* Edi: 00000005:
* Esi: 1BB294EC: 00000000 00000025 00000000 00000000 00000003 00
00000B
* Eax: 00000000:
* Ebx: 1BDCFFFD: 20000000 021BD5E0 00000000 E01BDD20 011BDD1F 00
000000
* Ecx: 1BB294EC: 00000000 00000025 00000000 00000000 00000003 00
00000B
* Edx: 00000E00:
* Eip: 00402453: E183088A 04E9830E 589D840F 4949001E E9830C74 0F
077404
* Ebp: 03F2D2A0: 03F2D2B4 005EEA86 00A4C638 03F2D2B0 03F2E3DC 03
F2E79C
* SegCs: 0000001B:
* EFlags: 00010246: 003D0052 005C005C 00410047 0049004C 0045004C 00
000049
* Esp: 03F2D28C: 1BB294EC 00445CB5 00000000 00000002 1BDCF8D0 03
F2D2B4
* SegSs: 00000023:
****************************************
************************************
***

Databases not displayed in Enterprise manager

Hi
I'm experiencing a weird problem, I have a sql server running with lots of different database and corresponding user to each database. Now the problem is that when a given user connects through EM the database in in EM list "no items" for all users except
one, and the sa. Now I have just reinstalled the server, thought it was a problem in the software, attached the databases and added the users all the same way, no special settings except for the assign of access as dbo to their own database.
Even creating a new database, and adding a new user results in the same stuff....
On my local development machine, doing the exact same thing dowsn't result in the mentioned behavoir.
WHY? (the desparate dba)
Found that everytime a user who cannot acces databases connects this shows up in the server log:
SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 04/16/04 22:38:12 spid 56
*
* Exception Address = 00402453 (RecBase::Resize(void) + 00000004 Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000000
* Input Buffer 68 bytes -
* exec sp_MSdbuseraccess N'db', N'%'
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B19FFF 0071a000
* ntdll 77F80000 77FFCFFF 0007d000
* KERNEL32 7C570000 7C627FFF 000b8000
* ADVAPI32 7C2D0000 7C331FFF 00062000
* RPCRT4 77D30000 77DA0FFF 00071000
* USER32 77E10000 77E74FFF 00065000
* GDI32 77F40000 77F7DFFF 0003e000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 78000000 78044FFF 00045000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 780A0000 780B1FFF 00012000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 7B470000 7B4BEFFF 0004f000
* SECUR32 7C340000 7C34EFFF 0000f000
* NETRAP 7B4C0000 7B4C5FFF 00006000
* SAMLIB 7B4D0000 7B4DEFFF 0000f000
* WS2_32 7B4E0000 7B4F3FFF 00014000
* WS2HELP 7B500000 7B507FFF 00008000
* WLDAP32 7B510000 7B539FFF 0002a000
* DNSAPI 7B540000 7B563FFF 00024000
* WSOCK32 7B570000 7B577FFF 00008000
* wmi 7B760000 7B763FFF 00004000
* ole32 7B870000 7B95EFFF 000ef000
* XOLEHLP 7B9E0000 7B9E7FFF 00008000
* MSDTCPRX 7B9F0000 7BAA6FFF 000b7000
* MTXCLU 7BAB0000 7BABFFFF 00010000
* VERSION 7BAC0000 7BAC6FFF 00007000
* LZ32 7BAD0000 7BAD5FFF 00006000
* CLUSAPI 7BAE0000 7BAEFFFF 00010000
* RESUTILS 7BAF0000 7BAFCFFF 0000d000
* USERENV 7C0F0000 7C150FFF 00061000
* rnr20 7BB00000 7BB0BFFF 0000c000
* iphlpapi 7BB50000 7BB62FFF 00013000
* ICMP 7BB70000 7BB74FFF 00005000
* MPRAPI 7BB80000 7BB96FFF 00017000
* OLEAUT32 7BBA0000 7BC3AFFF 0009b000
* ACTIVEDS 7BC40000 7BC6EFFF 0002f000
* ADSLDPC 7BC70000 7BC92FFF 00023000
* RTUTILS 7BCA0000 7BCADFFF 0000e000
* SETUPAPI 7BCB0000 7BD3DFFF 0008e000
* RASAPI32 7BD40000 7BD72FFF 00033000
* RASMAN 7BD80000 7BD90FFF 00011000
* TAPI32 7BDA0000 7BDC1FFF 00022000
* COMCTL32 7BDD0000 7BE53FFF 00084000
* SHLWAPI 7BE60000 7BEC4FFF 00065000
* DHCPCSVC 7BED0000 7BEE8FFF 00019000
* winrnr 011F0000 011F7FFF 00008000
* rasadhlp 01200000 01204FFF 00005000
* SSNETLIB 019D0000 019E5FFF 00016000
* SSNMPN70 410D0000 410D5FFF 00006000
* security 01CD0000 01CD3FFF 00004000
* crypt32 7C740000 7C7C6FFF 00087000
* MSASN1 01CE0000 01CEFFFF 00010000
* msafd 02100000 0211DFFF 0001e000
* wshtcpip 02160000 02166FFF 00007000
* SSmsLPCn 021F0000 021F6FFF 00007000
* ntdsapi 02290000 022A0FFF 00011000
* SQLFTQRY 02810000 0282CFFF 0001d000
* CLBCATQ 02830000 028BFFFF 00090000
* sqloledb 028E0000 02952FFF 00073000
* MSDART 02960000 0297EFFF 0001f000
* comdlg32 02980000 029BDFFF 0003e000
* SHELL32 029C0000 02C07FFF 00248000
* MSDATL3 02C10000 02C24FFF 00015000
* oledb32 02FB0000 03015FFF 00066000
* OLEDB32R 03020000 0302FFFF 00010000
* msv1_0 03050000 03070FFF 00021000
* xpstar 410F0000 41133FFF 00044000
* SQLUNIRL 10000000 1002CFFF 0002d000
* WINSPOOL 03080000 0309DFFF 0001e000
* MPR 030A0000 030AFFFF 00010000
* SQLRESLD 42AC0000 42AC6FFF 00007000
* SQLSVC 030B0000 030C6FFF 00017000
* ODBC32 030D0000 03101FFF 00032000
* odbcbcp 03110000 03115FFF 00006000
* W95SCM 41140000 4114BFFF 0000c000
* NDDEAPI 03120000 03126FFF 00007000
* odbcint 03270000 03285FFF 00016000
* SQLSVC 03290000 03295FFF 00006000
* xpstar 032A0000 032ABFFF 0000c000
* srchadm 034E0000 0351DFFF 0003e000
* mssadmws 03520000 03534FFF 00015000
* msi 03820000 03A23FFF 00204000
* athprxy 03A40000 03A47FFF 00008000
* rsabase 7CA00000 7CA22FFF 00023000
* xpsqlbot 04160000 04165FFF 00006000
* DBGHELP 042B0000 042C2FFF 00013000
* msdbi 04AF0000 04B0BFFF 0001c000
* sqlimage 09D20000 09D2CFFF 0000d000
*
* Edi: 00000005:
* Esi: 1BB294EC: 00000000 00000025 00000000 00000000 00000003 0000000B
* Eax: 00000000:
* Ebx: 1BDCFFFD: 20000000 021BD5E0 00000000 E01BDD20 011BDD1F 00000000
* Ecx: 1BB294EC: 00000000 00000025 00000000 00000000 00000003 0000000B
* Edx: 00000E00:
* Eip: 00402453: E183088A 04E9830E 589D840F 4949001E E9830C74 0F077404
* Ebp: 03F2D2A0: 03F2D2B4 005EEA86 00A4C638 03F2D2B0 03F2E3DC 03F2E79C
* SegCs: 0000001B:
* EFlags: 00010246: 003D0052 005C005C 00410047 0049004C 0045004C 00000049
* Esp: 03F2D28C: 1BB294EC 00445CB5 00000000 00000002 1BDCF8D0 03F2D2B4
* SegSs: 00000023:
************************************************** *****************************

Databases not displayed in Enterprise manager

H
I'm experiencing a weird problem, I have a sql server running with lots of different database and corresponding user to each database. Now the problem is that when a given user connects through EM the database in in EM list "no items" for all users except one, and the sa. Now I have just reinstalled the server, thought it was a problem in the software, attached the databases and added the users all the same way, no special settings except for the assign of access as dbo to their own database
Even creating a new database, and adding a new user results in the same stuff...
On my local development machine, doing the exact same thing dowsn't result in the mentioned behavoir
WHY? (the desparate dba)Found that everytime a user who cannot acces databases connects this shows up in the server log
SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
******************************************************************************
* BEGIN STACK DUMP
* 04/16/04 22:38:12 spid 5
* Exception Address = 00402453 (RecBase::Resize(void) + 00000004 Line 0+00000000
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATIO
* Access Violation occurred reading address 0000000
* Input Buffer 68 bytes
* exec sp_MSdbuseraccess N'db', N'%
*
* MODULE BASE END SIZ
* sqlservr 00400000 00B19FFF 0071a00
* ntdll 77F80000 77FFCFFF 0007d00
* KERNEL32 7C570000 7C627FFF 000b800
* ADVAPI32 7C2D0000 7C331FFF 0006200
* RPCRT4 77D30000 77DA0FFF 0007100
* USER32 77E10000 77E74FFF 0006500
* GDI32 77F40000 77F7DFFF 0003e00
* OPENDS60 41060000 41065FFF 0000600
* MSVCRT 78000000 78044FFF 0004500
* UMS 41070000 4107CFFF 0000d00
* SQLSORT 42AE0000 42B6FFFF 0009000
* MSVCIRT 780A0000 780B1FFF 0001200
* sqlevn70 41080000 41086FFF 0000700
* NETAPI32 7B470000 7B4BEFFF 0004f00
* SECUR32 7C340000 7C34EFFF 0000f00
* NETRAP 7B4C0000 7B4C5FFF 0000600
* SAMLIB 7B4D0000 7B4DEFFF 0000f00
* WS2_32 7B4E0000 7B4F3FFF 0001400
* WS2HELP 7B500000 7B507FFF 0000800
* WLDAP32 7B510000 7B539FFF 0002a00
* DNSAPI 7B540000 7B563FFF 0002400
* WSOCK32 7B570000 7B577FFF 0000800
* wmi 7B760000 7B763FFF 0000400
* ole32 7B870000 7B95EFFF 000ef00
* XOLEHLP 7B9E0000 7B9E7FFF 0000800
* MSDTCPRX 7B9F0000 7BAA6FFF 000b700
* MTXCLU 7BAB0000 7BABFFFF 0001000
* VERSION 7BAC0000 7BAC6FFF 0000700
* LZ32 7BAD0000 7BAD5FFF 0000600
* CLUSAPI 7BAE0000 7BAEFFFF 0001000
* RESUTILS 7BAF0000 7BAFCFFF 0000d00
* USERENV 7C0F0000 7C150FFF 0006100
* rnr20 7BB00000 7BB0BFFF 0000c00
* iphlpapi 7BB50000 7BB62FFF 0001300
* ICMP 7BB70000 7BB74FFF 0000500
* MPRAPI 7BB80000 7BB96FFF 0001700
* OLEAUT32 7BBA0000 7BC3AFFF 0009b00
* ACTIVEDS 7BC40000 7BC6EFFF 0002f00
* ADSLDPC 7BC70000 7BC92FFF 0002300
* RTUTILS 7BCA0000 7BCADFFF 0000e00
* SETUPAPI 7BCB0000 7BD3DFFF 0008e00
* RASAPI32 7BD40000 7BD72FFF 0003300
* RASMAN 7BD80000 7BD90FFF 0001100
* TAPI32 7BDA0000 7BDC1FFF 0002200
* COMCTL32 7BDD0000 7BE53FFF 0008400
* SHLWAPI 7BE60000 7BEC4FFF 0006500
* DHCPCSVC 7BED0000 7BEE8FFF 0001900
* winrnr 011F0000 011F7FFF 0000800
* rasadhlp 01200000 01204FFF 0000500
* SSNETLIB 019D0000 019E5FFF 0001600
* SSNMPN70 410D0000 410D5FFF 0000600
* security 01CD0000 01CD3FFF 0000400
* crypt32 7C740000 7C7C6FFF 0008700
* MSASN1 01CE0000 01CEFFFF 0001000
* msafd 02100000 0211DFFF 0001e00
* wshtcpip 02160000 02166FFF 00007000
* SSmsLPCn 021F0000 021F6FFF 00007000
* ntdsapi 02290000 022A0FFF 00011000
* SQLFTQRY 02810000 0282CFFF 0001d000
* CLBCATQ 02830000 028BFFFF 00090000
* sqloledb 028E0000 02952FFF 00073000
* MSDART 02960000 0297EFFF 0001f000
* comdlg32 02980000 029BDFFF 0003e000
* SHELL32 029C0000 02C07FFF 00248000
* MSDATL3 02C10000 02C24FFF 00015000
* oledb32 02FB0000 03015FFF 00066000
* OLEDB32R 03020000 0302FFFF 00010000
* msv1_0 03050000 03070FFF 00021000
* xpstar 410F0000 41133FFF 00044000
* SQLUNIRL 10000000 1002CFFF 0002d000
* WINSPOOL 03080000 0309DFFF 0001e000
* MPR 030A0000 030AFFFF 00010000
* SQLRESLD 42AC0000 42AC6FFF 00007000
* SQLSVC 030B0000 030C6FFF 00017000
* ODBC32 030D0000 03101FFF 00032000
* odbcbcp 03110000 03115FFF 00006000
* W95SCM 41140000 4114BFFF 0000c000
* NDDEAPI 03120000 03126FFF 00007000
* odbcint 03270000 03285FFF 00016000
* SQLSVC 03290000 03295FFF 00006000
* xpstar 032A0000 032ABFFF 0000c000
* srchadm 034E0000 0351DFFF 0003e000
* mssadmws 03520000 03534FFF 00015000
* msi 03820000 03A23FFF 00204000
* athprxy 03A40000 03A47FFF 00008000
* rsabase 7CA00000 7CA22FFF 00023000
* xpsqlbot 04160000 04165FFF 00006000
* DBGHELP 042B0000 042C2FFF 00013000
* msdbi 04AF0000 04B0BFFF 0001c000
* sqlimage 09D20000 09D2CFFF 0000d000
*
* Edi: 00000005:
* Esi: 1BB294EC: 00000000 00000025 00000000 00000000 00000003 0000000B
* Eax: 00000000:
* Ebx: 1BDCFFFD: 20000000 021BD5E0 00000000 E01BDD20 011BDD1F 00000000
* Ecx: 1BB294EC: 00000000 00000025 00000000 00000000 00000003 0000000B
* Edx: 00000E00:
* Eip: 00402453: E183088A 04E9830E 589D840F 4949001E E9830C74 0F077404
* Ebp: 03F2D2A0: 03F2D2B4 005EEA86 00A4C638 03F2D2B0 03F2E3DC 03F2E79C
* SegCs: 0000001B:
* EFlags: 00010246: 003D0052 005C005C 00410047 0049004C 0045004C 00000049
* Esp: 03F2D28C: 1BB294EC 00445CB5 00000000 00000002 1BDCF8D0 03F2D2B4
* SegSs: 00000023:
*******************************************************************************

Databases in EM diapppeared when added 6 db's to a total 16 db's

After adding 6 databases to a server for a total 16
databases, the databases in Enterprise Manager just
disappeared. However, it had no problems in viewing the
databases using either DBArtisan or Query Analyzer. Is
this a bug in EM?HI,
Can you try applying the latest service pack (SP3a) in your client and
verify the same.
No more clues coming to my mind.
Thanks
Hari
MCDBA
"Jeffrey" <jwang@.dot.state.tx.us> wrote in message
news:1b5d01c42709$7d4d3fa0$a601280a@.phx.gbl...
> After adding 6 databases to a server for a total 16
> databases, the databases in Enterprise Manager just
> disappeared. However, it had no problems in viewing the
> databases using either DBArtisan or Query Analyzer. Is
> this a bug in EM?|||I was running into this error on SQL 2000 SP3a.
Thanks.
Jeffrey

>--Original Message--
>HI,
>Can you try applying the latest service pack (SP3a) in
your client and
>verify the same.
>No more clues coming to my mind.
>Thanks
>Hari
>MCDBA
>
>"Jeffrey" <jwang@.dot.state.tx.us> wrote in message
>news:1b5d01c42709$7d4d3fa0$a601280a@.phx.gbl...
>
>.
>

Databases in EM diapppeared when added 6 db's to a total 16 db's

After adding 6 databases to a server for a total 16
databases, the databases in Enterprise Manager just
disappeared. However, it had no problems in viewing the
databases using either DBArtisan or Query Analyzer. Is
this a bug in EM?
HI,
Can you try applying the latest service pack (SP3a) in your client and
verify the same.
No more clues coming to my mind.
Thanks
Hari
MCDBA
"Jeffrey" <jwang@.dot.state.tx.us> wrote in message
news:1b5d01c42709$7d4d3fa0$a601280a@.phx.gbl...
> After adding 6 databases to a server for a total 16
> databases, the databases in Enterprise Manager just
> disappeared. However, it had no problems in viewing the
> databases using either DBArtisan or Query Analyzer. Is
> this a bug in EM?
|||I was running into this error on SQL 2000 SP3a.
Thanks.
Jeffrey

>--Original Message--
>HI,
>Can you try applying the latest service pack (SP3a) in
your client and
>verify the same.
>No more clues coming to my mind.
>Thanks
>Hari
>MCDBA
>
>"Jeffrey" <jwang@.dot.state.tx.us> wrote in message
>news:1b5d01c42709$7d4d3fa0$a601280a@.phx.gbl...
>
>.
>

Databases in EM diapppeared when added 6 db's to a total 16 db's

After adding 6 databases to a server for a total 16
databases, the databases in Enterprise Manager just
disappeared. However, it had no problems in viewing the
databases using either DBArtisan or Query Analyzer. Is
this a bug in EM?There is a right click option in 'Databases'
called 'REFRESH' !!!!!
>--Original Message--
>After adding 6 databases to a server for a total 16
>databases, the databases in Enterprise Manager just
>disappeared. However, it had no problems in viewing the
>databases using either DBArtisan or Query Analyzer. Is
>this a bug in EM?
>.
>|||I tried, but still can not view the databases.
Thanks.
>--Original Message--
>There is a right click option in 'Databases'
>called 'REFRESH' !!!!!
>
>>--Original Message--
>>After adding 6 databases to a server for a total 16
>>databases, the databases in Enterprise Manager just
>>disappeared. However, it had no problems in viewing the
>>databases using either DBArtisan or Query Analyzer. Is
>>this a bug in EM?
>>.
>.
>|||HI,
Can you try applying the latest service pack (SP3a) in your client and
verify the same.
No more clues coming to my mind.
Thanks
Hari
MCDBA
"Jeffrey" <jwang@.dot.state.tx.us> wrote in message
news:1b5d01c42709$7d4d3fa0$a601280a@.phx.gbl...
> After adding 6 databases to a server for a total 16
> databases, the databases in Enterprise Manager just
> disappeared. However, it had no problems in viewing the
> databases using either DBArtisan or Query Analyzer. Is
> this a bug in EM?|||I was running into this error on SQL 2000 SP3a.
Thanks.
Jeffrey
>--Original Message--
>HI,
>Can you try applying the latest service pack (SP3a) in
your client and
>verify the same.
>No more clues coming to my mind.
>Thanks
>Hari
>MCDBA
>
>"Jeffrey" <jwang@.dot.state.tx.us> wrote in message
>news:1b5d01c42709$7d4d3fa0$a601280a@.phx.gbl...
>> After adding 6 databases to a server for a total 16
>> databases, the databases in Enterprise Manager just
>> disappeared. However, it had no problems in viewing the
>> databases using either DBArtisan or Query Analyzer. Is
>> this a bug in EM?
>
>.
>

Databases folder empty in Enterprise Manager

Hi all,
I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
client tools on the same machine. When I open Enterprise Manager, the
Databases folder is empty. Even the master database plus other default
databases (msdb, ...) are not shown. I have made sure the "show system
databases and objects" setting is checked. This happens whether I
connect to the MSDE server using the sa account or Windows
authentication. Also the Query Analyzer utility doesn't work as well.
It opens, but the command window has no place to type SQL commands, and
the Object Browser doesn't show any databases.
I also have a number of old databases (.mdf and .ldf files) that I want
to attach to this instance. These databases have been originally
copied from another machine, and have been working on this machine with
a previous installation of SQL Server Personal Edition. When I open
the attach databases window in Enterprise Manager, and select a mdf
file, and click OK, at first nothing happens (no feedback, and the
dialog even doesn't go away) but clicking OK a second time gives an
error message stating that a database with the same name already exists
(and yet the dialog remains open.) Any further actions will take
Enterprise Manager down by a crash.
Then I tried connecting to MSDE using osql.exe, and a "USE master;
SELECT * FROM sysdatabases;" shows the attached db as well, and I can
even switch to that db and select/insert/update/delete data in it. And
using the sp_attach_db stored procedure in osql.exe works without any
errors. But still none of the databases listed in sysdatabases is
shown in Enterprise Manager.
I could go on working in osql.exe but I'm not very knowledgable in
working with MSDE using SQL commands, and I'd rather do the same in
Enterprise Manager. I have the exact same setup on other workstations
and they work beautifully. Upgrding MSDE to SP4 and client tools to
SP3 didn't solve anything as well.
Can someone help me there please?
Thanks!
Ehsan
The MSDE edition of SQL Server was developed to answer the needs of some
people who don't want to spend money on buying SQL Server. MSDE is available
to anyone but has some restrictions, some of them are:
- 2 GB maximum capacity
- Doesn't work with Graphic Administration Tools like Enterprise Manager.
The administration must be made by code (T-SQL).
I don't know the kind of needs you have but try to build an Access project
and link the database tables to it. You can build views directly and have
access to table objects.
"ehsan.akhgari@.gmail.com" wrote:

> Hi all,
> I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
> client tools on the same machine. When I open Enterprise Manager, the
> Databases folder is empty. Even the master database plus other default
> databases (msdb, ...) are not shown. I have made sure the "show system
> databases and objects" setting is checked. This happens whether I
> connect to the MSDE server using the sa account or Windows
> authentication. Also the Query Analyzer utility doesn't work as well.
> It opens, but the command window has no place to type SQL commands, and
> the Object Browser doesn't show any databases.
> I also have a number of old databases (.mdf and .ldf files) that I want
> to attach to this instance. These databases have been originally
> copied from another machine, and have been working on this machine with
> a previous installation of SQL Server Personal Edition. When I open
> the attach databases window in Enterprise Manager, and select a mdf
> file, and click OK, at first nothing happens (no feedback, and the
> dialog even doesn't go away) but clicking OK a second time gives an
> error message stating that a database with the same name already exists
> (and yet the dialog remains open.) Any further actions will take
> Enterprise Manager down by a crash.
> Then I tried connecting to MSDE using osql.exe, and a "USE master;
> SELECT * FROM sysdatabases;" shows the attached db as well, and I can
> even switch to that db and select/insert/update/delete data in it. And
> using the sp_attach_db stored procedure in osql.exe works without any
> errors. But still none of the databases listed in sysdatabases is
> shown in Enterprise Manager.
> I could go on working in osql.exe but I'm not very knowledgable in
> working with MSDE using SQL commands, and I'd rather do the same in
> Enterprise Manager. I have the exact same setup on other workstations
> and they work beautifully. Upgrding MSDE to SP4 and client tools to
> SP3 didn't solve anything as well.
> Can someone help me there please?
> Thanks!
> Ehsan
>
|||Thanks for your reply,
I did not know about this restriction for MSDE. That explains
everything now.
Ehsan

Databases folder empty in Enterprise Manager

Hi all,
I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
client tools on the same machine. When I open Enterprise Manager, the
Databases folder is empty. Even the master database plus other default
databases (msdb, ...) are not shown. I have made sure the "show system
databases and objects" setting is checked. This happens whether I
connect to the MSDE server using the sa account or Windows
authentication. Also the Query Analyzer utility doesn't work as well.
It opens, but the command window has no place to type SQL commands, and
the Object Browser doesn't show any databases.
I also have a number of old databases (.mdf and .ldf files) that I want
to attach to this instance. These databases have been originally
copied from another machine, and have been working on this machine with
a previous installation of SQL Server Personal Edition. When I open
the attach databases window in Enterprise Manager, and select a mdf
file, and click OK, at first nothing happens (no feedback, and the
dialog even doesn't go away) but clicking OK a second time gives an
error message stating that a database with the same name already exists
(and yet the dialog remains open.) Any further actions will take
Enterprise Manager down by a crash.
Then I tried connecting to MSDE using osql.exe, and a "USE master;
SELECT * FROM sysdatabases;" shows the attached db as well, and I can
even switch to that db and select/insert/update/delete data in it. And
using the sp_attach_db stored procedure in osql.exe works without any
errors. But still none of the databases listed in sysdatabases is
shown in Enterprise Manager.
I could go on working in osql.exe but I'm not very knowledgable in
working with MSDE using SQL commands, and I'd rather do the same in
Enterprise Manager. I have the exact same setup on other workstations
and they work beautifully. Upgrding MSDE to SP4 and client tools to
SP3 didn't solve anything as well.
Can someone help me there please?
Thanks!
EhsanThe MSDE edition of SQL Server was developed to answer the needs of some
people who don't want to spend money on buying SQL Server. MSDE is available
to anyone but has some restrictions, some of them are:
- 2 GB maximum capacity
- Doesn't work with Graphic Administration Tools like Enterprise Manager.
The administration must be made by code (T-SQL).
I don't know the kind of needs you have but try to build an Access project
and link the database tables to it. You can build views directly and have
access to table objects.
"ehsan.akhgari@.gmail.com" wrote:
> Hi all,
> I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
> client tools on the same machine. When I open Enterprise Manager, the
> Databases folder is empty. Even the master database plus other default
> databases (msdb, ...) are not shown. I have made sure the "show system
> databases and objects" setting is checked. This happens whether I
> connect to the MSDE server using the sa account or Windows
> authentication. Also the Query Analyzer utility doesn't work as well.
> It opens, but the command window has no place to type SQL commands, and
> the Object Browser doesn't show any databases.
> I also have a number of old databases (.mdf and .ldf files) that I want
> to attach to this instance. These databases have been originally
> copied from another machine, and have been working on this machine with
> a previous installation of SQL Server Personal Edition. When I open
> the attach databases window in Enterprise Manager, and select a mdf
> file, and click OK, at first nothing happens (no feedback, and the
> dialog even doesn't go away) but clicking OK a second time gives an
> error message stating that a database with the same name already exists
> (and yet the dialog remains open.) Any further actions will take
> Enterprise Manager down by a crash.
> Then I tried connecting to MSDE using osql.exe, and a "USE master;
> SELECT * FROM sysdatabases;" shows the attached db as well, and I can
> even switch to that db and select/insert/update/delete data in it. And
> using the sp_attach_db stored procedure in osql.exe works without any
> errors. But still none of the databases listed in sysdatabases is
> shown in Enterprise Manager.
> I could go on working in osql.exe but I'm not very knowledgable in
> working with MSDE using SQL commands, and I'd rather do the same in
> Enterprise Manager. I have the exact same setup on other workstations
> and they work beautifully. Upgrding MSDE to SP4 and client tools to
> SP3 didn't solve anything as well.
> Can someone help me there please?
> Thanks!
> Ehsan
>|||Thanks for your reply,
I did not know about this restriction for MSDE. That explains
everything now.
Ehsan

Databases folder empty in Enterprise Manager

Hi all,
I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
client tools on the same machine. When I open Enterprise Manager, the
Databases folder is empty. Even the master database plus other default
databases (msdb, ...) are not shown. I have made sure the "show system
databases and objects" setting is checked. This happens whether I
connect to the MSDE server using the sa account or Windows
authentication. Also the Query Analyzer utility doesn't work as well.
It opens, but the command window has no place to type SQL commands, and
the Object Browser doesn't show any databases.
I also have a number of old databases (.mdf and .ldf files) that I want
to attach to this instance. These databases have been originally
copied from another machine, and have been working on this machine with
a previous installation of SQL Server Personal Edition. When I open
the attach databases window in Enterprise Manager, and select a mdf
file, and click OK, at first nothing happens (no feedback, and the
dialog even doesn't go away) but clicking OK a second time gives an
error message stating that a database with the same name already exists
(and yet the dialog remains open.) Any further actions will take
Enterprise Manager down by a crash.
Then I tried connecting to MSDE using osql.exe, and a "USE master;
SELECT * FROM sysdatabases;" shows the attached db as well, and I can
even switch to that db and select/insert/update/delete data in it. And
using the sp_attach_db stored procedure in osql.exe works without any
errors. But still none of the databases listed in sysdatabases is
shown in Enterprise Manager.
I could go on working in osql.exe but I'm not very knowledgable in
working with MSDE using SQL commands, and I'd rather do the same in
Enterprise Manager. I have the exact same setup on other workstations
and they work beautifully. Upgrding MSDE to SP4 and client tools to
SP3 didn't solve anything as well.
Can someone help me there please?
Thanks!
EhsanThe MSDE edition of SQL Server was developed to answer the needs of some
people who don't want to spend money on buying SQL Server. MSDE is available
to anyone but has some restrictions, some of them are:
- 2 GB maximum capacity
- Doesn't work with Graphic Administration Tools like Enterprise Manager.
The administration must be made by code (T-SQL).
I don't know the kind of needs you have but try to build an Access project
and link the database tables to it. You can build views directly and have
access to table objects.
"ehsan.akhgari@.gmail.com" wrote:

> Hi all,
> I have installed MSDE 2000 SP3a on a workstation, as well as SQL Server
> client tools on the same machine. When I open Enterprise Manager, the
> Databases folder is empty. Even the master database plus other default
> databases (msdb, ...) are not shown. I have made sure the "show system
> databases and objects" setting is checked. This happens whether I
> connect to the MSDE server using the sa account or Windows
> authentication. Also the Query Analyzer utility doesn't work as well.
> It opens, but the command window has no place to type SQL commands, and
> the Object Browser doesn't show any databases.
> I also have a number of old databases (.mdf and .ldf files) that I want
> to attach to this instance. These databases have been originally
> copied from another machine, and have been working on this machine with
> a previous installation of SQL Server Personal Edition. When I open
> the attach databases window in Enterprise Manager, and select a mdf
> file, and click OK, at first nothing happens (no feedback, and the
> dialog even doesn't go away) but clicking OK a second time gives an
> error message stating that a database with the same name already exists
> (and yet the dialog remains open.) Any further actions will take
> Enterprise Manager down by a crash.
> Then I tried connecting to MSDE using osql.exe, and a "USE master;
> SELECT * FROM sysdatabases;" shows the attached db as well, and I can
> even switch to that db and select/insert/update/delete data in it. And
> using the sp_attach_db stored procedure in osql.exe works without any
> errors. But still none of the databases listed in sysdatabases is
> shown in Enterprise Manager.
> I could go on working in osql.exe but I'm not very knowledgable in
> working with MSDE using SQL commands, and I'd rather do the same in
> Enterprise Manager. I have the exact same setup on other workstations
> and they work beautifully. Upgrding MSDE to SP4 and client tools to
> SP3 didn't solve anything as well.
> Can someone help me there please?
> Thanks!
> Ehsan
>|||Thanks for your reply,
I did not know about this restriction for MSDE. That explains
everything now.
Ehsan

Database/table help

Almost embarassed to ask this but here it goes...

Need to create a database, which will store employee, manager and department. Could someone please help me in creating these tables and their relationships. Looking for something efficient and simple...where this employee works in this department, managed by manager.

Thank you.

May be you should use a simpler product like MS Access to see how you can create these tables and establish relations between the tables.|||

hi,

perhaps you can have a look at http://www.databaseanswers.org/data_models/hr_intro.htm..

the Microsoft database sample AdventureWorks include a human resource implementation as well.. you can see/download the diagram at http://www.microsoft.com/downloads/details.aspx?FamilyID=0f6e0bcf-a1b5-4760-8d79-67970f93d5ff&DisplayLang=en

regards