DataSource uploads as text file type

Hi,
I have a new installation of SQLExpress ADV with RS installed on XP Pro.
When I try to upload an rds file (which has already been running
successfully on a w2k3 server), it uploads as a text file and NOT as a
Datasource.
The associated report does of course not work.
Anyone seen this before - or know how to fix it please '.
Thanks
Regards
GrahamHi Oxns,
Thank you for your posting!
From your description, my understanding of this issue is: you want to
upload the report data source file as a shared data source in the report
manager. If I misunderstood your concern, please feel free to let me know.
You cannot upload a report data source (.rds) file to create a shared data
source. An .rds file is used only in Report Designer. It cannot provide the
content for a shared data source item that you define and manage through
Report Manager or Management Studio. As an alternative to uploading, you
can write a script that creates a shared data source based on a .rds file.
Please refer to the sample script PublishSamplReports.rss file in the
Samples. By default, scripting samples are located in C:\Program
Files\Microsoft SQL Server\90\Samples\Reporting Services\Script Samples.
Here are the articles for your reference:
Script Samples (Reporting Services)
http://msdn2.microsoft.com/en-us/library/ms160854(d=ide).aspx
Uploading Files to a Folder
http://msdn2.microsoft.com/en-us/library/ms156300(d=ide).aspx
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Oxns,
How are you doing on this issue? Have you got any progress or does Wei's
last reply help you some on this? If the problem is not resolved or there
is anything else we can help, please feel free to post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

DataSource has 2 instances that don't exist

Using VS05 SP1 Pro SQL Express…

In converting a program from VS03/MSDE, long ago I installed SQL 2005 Express with Advanced Services and everything was fine.Windows Update has recently been failing to install SQL 2005 Express with Advanced Services SP2.After no answers from the forums, and logs that were of no help, I decided to uninstall SQL 2005 Express with Advanced Services and reinstall SQL 2005 Express (basic version).As a test run, I did it on a desk top, no problems what so ever.

However, on my laptop, it has been a nightmare.

Question 1) in control panel, add/remove programs, all of SQL 2005 Express with Advanced Services uninstalled fine except one item - I am unable to uninstall MS SQL 2005 Backward Compatibility, getting the error message

A network error occurred while attempting to read from the file

c:\windows\installer\sqlserver2005_bc.msi

That file is not on the hard disk.

After installing SQL 2005 Express (the basic version), this problem persists and I cannot uninstall MS SQL 2005 Backward Compatibility for the same reason.

How can I get rid of MS SQL 2005 Backward Compatibility?

Question 2) Windows update still is trying to download and install SQL 2005 Express with Advanced Services SP2, even though I have uninstalled it.How to manually get rid of whatever settings are triggering this?

Thanks!

Bob

Using VS05 SP1 Pro SQL Express…

Server Explorer, Add Connection, Advance Settings Button, DataSource lists 3 options:

.\SQLEXPRESS

.\CSoltuion

.\MSSQLSERVER

I am only interested in the first one, SQLEXPRES, and would like to remove the other two (MSSQLSERVER is actually disabled because if you try to start it you get an error message The request failed or the server did not respond in a timely fashion).In Control Panel, Add/Remove Programs, MS SQL Server 2005, Remove Button, it gives me the option to remove only

CSoltuion

SQLEXPRESS

If I choose CSoltuion to remove, it immediately does nothing and goes back to the add/remove screen.If I choose Remove for MS SQL Server 2005, CSoltuion is still there.

How do I get rid of

.\CSoltuion

.\MSSQLSERVER

Thanks!

Bob

|||

Using VS05 SP1 Pro SQL Express…

Question 1) Is the only way to add a new named SQL instance to run the SQL Express (download file SQLEXPR32.EXE) and choose the name where it asks you to? This is incredibly time consuming and often you spend a lot of time to have it fail.

Question 2) In Add/Remove programs MS SQL Server 2005, I have two named instances

SQLEXPRESS

CSoltuion

If I choose either of them to be removed, nothing happens, and it instantly returns to the add/remove screen and they are still there. They are not listed as services under manager computer.

If I try add them by running SQLEXPR32.EXE, they are not listed as existing named instances (there is a button to check that before you choose a name), but when I get to the end (again, much time wasted), the install fails saying the named instance already exists.

How do I get rid of these two named instances?

Question 3) The only way I have been able to get a named instance to work is to choose a name that has never been used before, such as SQLForTheFirstTime, which is ridiculous.

I want a named instance only of SQLEXPRESS…How do I do that?

Thanks

Bob

|||

I'm looking into this Bob. In the future, please don't post the same question multiple times, it doesn't get you an answer any faster.

Mike

|||

Hi Bob,

Question 1) Is the only way to add a new named SQL instance to run the SQL Express (download file SQLEXPR32.EXE) and choose the name where it asks you to? This is incredibly time consuming and often you spend a lot of time to have it fail.

Yes, each named instance is a completely separate copy of SQL Express. There is no way to get a separate copy other than to install it.

Question 2) In Add/Remove programs MS SQL Server 2005, I have two named instances

SQLEXPRESS

CSoltuion

If I choose either of them to be removed, nothing happens, and it instantly returns to the add/remove screen and they are still there. They are not listed as services under manager computer.

If I try add them by running SQLEXPR32.EXE, they are not listed as existing named instances (there is a button to check that before you choose a name), but when I get to the end (again, much time wasted), the install fails saying the named instance already exists.

How do I get rid of these two named instances?

So you're seeing Microsoft SQL Server 2005 in Add/Remove Programs, and the report lists the two instances you've named, but they don't uninstall. When you say they are not listed under Manage Computer, you're talking about the list of Services, right? It seems like you've already tried to remove these instances from your computer but something went wrong during the uninstall, do you remember removing these previously before noticing the failure you've described?

I have some ideas for getting rid of these, but it will royally mess up SQL Server if you actually have it installed. We need to be sure these really aren't there. Are there any SQL Tools on the Start menu? For example, can you find Start | All Programs | Microsoft SQL Server 2005 | Configuration Tools | SQL Server Configuration Manager? If it's there, launch it and see if it lists any instances of SQL Server and check their state. (Started, Stopped, etc.) If they are stopped, try to start them.

If there is nothing on the Start menu and/or you can't start any of the instances on your computer, you can try using the Windows Installer Cleanup Utility. This doesn't actually remove programs from your computer, it just removes the entries for the program in the windows installer registry so that windows installer doesn't think it's installed. This will really break any SQL Components that you do have installed, so be carful. Run the utility and try to remove the entry for Microsoft SQL Server 2005. Once you've done that, try installing again.

It's possible that you could still have problems based on SQL registry entries, but lets cross that bridge when we get to it.

|||

As to your first paragraph, yes to everything.

Below is in chronological order after reading your message...

SQL Server Management Studio Express, Server Name, Browse For Servers shows the following local servers

(all prefaced by local machine name)

MICROSOFTSMLBIZ (for Outlook Business Contact Manager, MSDE Format I think)

MICROSOFTBCM (for Outlook Business Contact Manager, MSDE Format I think)

(MACHINE NAME ONLY)

SQLEXPRESS

CSOLUTION

SQLTEST

SQLEXPRESSDATA (this is the only one that works)

SQL Server Configuration Manager

SQL Server 2005 Services shows

SQLEXPRESS

SQLTEST

MSSQLSERVER

SQLEXPRESSDATA (this is the only one that works)

SQL Server 2005 Network Configuration shows

CSOLUTION (note this is not shown above)

SQLEXPRESS

SQLTEST

MSSQLSERVER

SQLEXPRESSDATA (this is the only one that works)

I then ran the Windows Install Clean up on

CSOLUTION

SQLEXPRESS

The only other one listed was

SQLEXPRESSDATA

Which I did not run it on because it is the only one working.

In add remove programs SQL 2005 remove button shows

CSOLUTION

SQLEXPRESS

SQLEXPRESSDATA

I clicked the radio button forSQLEXPRESS to remove it, and it tried to remove SQLEXPRESSDATA (the one that works), so I cancelled. I confirmed SQLEXPRESSDATA still works.

In computer manager services, it shows the following (note that the ones that did not start did not show before running Windows Install Cleanup)

SQLEXPRESS

SQLEXPRESSDATA (this is the only one that starts).

SQLTEST

MSSQLSERVER

SQL Server Management Studio Express and SQL Server Configuration Manager show the same thing after running Windows Install Cleanup.

The only way I have found to install a new instance is to use a name that has never been used before.

Also, when you create a new named instance, C:\Program Files\Microsoft SQL Server\MSSQL.4 starts at 4 (why does it not start at 1?) . SQLEXPRESSDATA (the only one that works) uses MSSQL.4

Where do we go from here? It looks like a real mess.

Thanks for your help.

Bob

|||

Quick question on these forums -

can you Alt_PrtScrn and Paste a dialog box into a forum, without having to type it all out like it did above, to show you what you are asking for?

Bob

|||

Try this:

Remove –Windows Installer Clean-Up Tool
http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe

|||

Hi Bob,

Answer to quick question: No, you can't paste graphics into the forum posts, I wish you could.

Since all the standard ways to remove SQL Express seem to be failing we'll have to go a bit more old school. Follow the instructions in this KB to manually remove SQL from the machine. You may need to do some of the steps for each instance you're wanting to get rid of. This should get you back to a clean state that will allow you to install the default named instance of SQL Express.

Mike

|||

Based on the document, there were two options, here are the results:

Option 1 - Ran ARPWrapper.exe /Remove on CSolution, it did nothing. ARPWrapper.exe /Remove is the same as runing via the add/remove programs.

Option 2 - Looked at each GUID under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, there was no Microsoft SQL entry.

No other approches in the document.

If I do a search on CSolution in the registry, there are entires, but I am hesitant to just start deleteing any I find.

Any other ideas?

Thanks

Bob

|||

Hi Bob,

Where are you finding the entries for CSolution, and for that matter, SQLEXPRESS? Don't start deleting just yet, I'm discussing this with our setup team to get the right solution.

Mike

|||

You can also find the product codes if you look in the registry under the InstId keys, located in a path like this:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.*\Setup

There will be one MSSQL.* key for each instance, numbered probably in order. Something like MSSQL.1, MSSQL.2, and so on.

|||

Under VS03, the name of the solution was CSolution as well as the name of the SQL MSDE Instance.

When we upgraded to VS05/SQL Express, the name of the solution was changed to CSolution_Telephony and the SQL instance was first left at Csolution but then changed to SQLExpress (without CSolution being uninstalled).Everything worked fine for a long time.

All the SQL problems started when Windows Update could not install the SP2 for SQL Express Advanced, so we uninstalled it and reinstalled the basic SQL Express.We are now using a named instance of SQLExpressData which works fine.

This is a development machine, so it has VS05 Pro and VB express on it.

Registry Search for CSOLUTION

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\Application\CSOLUTION

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\Application\MSSQL$CSOLUTION

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\Application\SQLAgent$CSOLUTION

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\Application\SQLCTR$CSOLUTION

Registry Search for SQLEXPRESS

My Computer\HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\tools\ShellSEM\DataProject

My Computer\HKEY_CURRENT_USER\Software\Microsoft\VBExpress\8.0\DataProject

My Computer\HKEY_CURRENT_USER\Software\Microsoft\VBExpress\8.0\Find

My Computer\HKEY_CURRENT_USER\Software\Microsoft\VWDExprss\8.0\DataProject

Thansk!

Bob

|||

Here are two more that did not appear in the find, but where there when I looked at these specific places based on another post in this thread.

Registry for CSOLUTION

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2

Registry for SQLEXPRESS

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1

This is an odd one…

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.5 (no value set).

Only MSSQL.4, which is SQLExpressData, appear as folders in Program\MS SQL SERVER

Thanks,

Bob Day

|||

Hi Bob,

Per R. Greens instructions, take a look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.*\Setup. The * in this case would be 2 for CSOLUTION and 1 for SQLEXPRESS. You shoud be able to find the Product Code listed there and use that product code with msiexec as described in the KB article.

Let us know how what happens.

Mike

sql

Databse Link will not connect

I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).

I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.

The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.

Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.

I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.

Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.

I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.

I can connect via a dblink TO these new instances from the older boxes
fine.

I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.

Must be some sort of permissions problem, but I don't know what else to
check - - -

Please help!!

THANK YOU!!Not completely sure what you mean by a dblink, but what SQL permissions
do the Administrators have on each server? Are you sure the
BUILTIN/Administrators Windows group have the appropriate permissions
on the databases you want to select from?

Stu

traceable1 wrote:

Quote:

Originally Posted by

I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).
>
I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.
>
The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.
>
Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.
>
I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.
>
Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.
>
I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.
>
I can connect via a dblink TO these new instances from the older boxes
fine.
>
I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.
>
Must be some sort of permissions problem, but I don't know what else to
check - - -
>
Please help!!
>
THANK YOU!!

|||Thank you!

By dblink I am referring to a linked server. (I apologize - I come
from an Oracle background).

The BUILTIN/Administrators group has all of the System Roles and it
still did not work.
Other boxes have links into the server/instance which work fine, and
the new server can link to other servers.
It's strange because it's just this one combination that does not work.

Group A: oldest servers; non-clustered; Win 2003 SP1

Group B: medium servers; 1 a/p cluster; 2 non-clustered; Win 2003 SP1

Group C: newest servers; 3 a/a clusters; Win 2003 R2

All SQL Server 2000 SP4

Group A can link to Group B
Group A can link to Group C
Group B can link to Group A
Group B can link to Group C
Group C can link to Group A
Group C CANNOT link to Group A if logged in using Windows
Authentication

All of the links are set up using "sa".

Stu wrote:

Quote:

Originally Posted by

Not completely sure what you mean by a dblink, but what SQL permissions
do the Administrators have on each server? Are you sure the
BUILTIN/Administrators Windows group have the appropriate permissions
on the databases you want to select from?
>
Stu
>
>
traceable1 wrote:

Quote:

Originally Posted by

I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).

I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.

The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.

Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.

I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.

Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.

I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.

I can connect via a dblink TO these new instances from the older boxes
fine.

I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.

Must be some sort of permissions problem, but I don't know what else to
check - - -

Please help!!

THANK YOU!!

|||You may want to google "double-hop" and SQL Server; I'm not sure that I
understand your scenario, but a few articles might ring true.

HTH,
Stu

traceable1 wrote:

Quote:

Originally Posted by

Thank you!
>
By dblink I am referring to a linked server. (I apologize - I come
from an Oracle background).
>
The BUILTIN/Administrators group has all of the System Roles and it
still did not work.
Other boxes have links into the server/instance which work fine, and
the new server can link to other servers.
It's strange because it's just this one combination that does not work.
>
>
Group A: oldest servers; non-clustered; Win 2003 SP1
>
Group B: medium servers; 1 a/p cluster; 2 non-clustered; Win 2003 SP1
>
Group C: newest servers; 3 a/a clusters; Win 2003 R2
>
All SQL Server 2000 SP4
>
Group A can link to Group B
Group A can link to Group C
Group B can link to Group A
Group B can link to Group C
Group C can link to Group A
Group C CANNOT link to Group A if logged in using Windows
Authentication
>
All of the links are set up using "sa".
>
>
>
>
>
>
Stu wrote:

Quote:

Originally Posted by

Not completely sure what you mean by a dblink, but what SQL permissions
do the Administrators have on each server? Are you sure the
BUILTIN/Administrators Windows group have the appropriate permissions
on the databases you want to select from?

Stu

traceable1 wrote:

Quote:

Originally Posted by

I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).
>
I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.
>
The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.
>
Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.
>
I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.
>
Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.
>
I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.
>
I can connect via a dblink TO these new instances from the older boxes
fine.
>
I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.
>
Must be some sort of permissions problem, but I don't know what else to
check - - -
>
Please help!!
>
THANK YOU!!

|||Thanks -

we're not double-hopping.

If you go to Enterprise Manager, under Security there is "Linked
Servers".

If I am on one of the boxes in Group C, I am unable to open the link to
any of the instances in Group B if I am logged into the instance using
Windows Authentication. (Sorry I had a typo in the last message).

I've recently discovered that if I change the port back to 1433, the
database link will work. However, I am uncomfortable going back to the
default port.
All of my other links work fine.

Also, the servers in Group C are using 64-bit Windows (but 32-bit SQL).

thanks,
tc

Stu wrote:

Quote:

Originally Posted by

You may want to google "double-hop" and SQL Server; I'm not sure that I
understand your scenario, but a few articles might ring true.
>
HTH,
Stu
>
>
traceable1 wrote:

Quote:

Originally Posted by

Thank you!

By dblink I am referring to a linked server. (I apologize - I come
from an Oracle background).

The BUILTIN/Administrators group has all of the System Roles and it
still did not work.
Other boxes have links into the server/instance which work fine, and
the new server can link to other servers.
It's strange because it's just this one combination that does not work.

Group A: oldest servers; non-clustered; Win 2003 SP1

Group B: medium servers; 1 a/p cluster; 2 non-clustered; Win 2003 SP1

Group C: newest servers; 3 a/a clusters; Win 2003 R2

All SQL Server 2000 SP4

Group A can link to Group B
Group A can link to Group C
Group B can link to Group A
Group B can link to Group C
Group C can link to Group A
Group C CANNOT link to Group A if logged in using Windows
Authentication

All of the links are set up using "sa".

Stu wrote:

Quote:

Originally Posted by

Not completely sure what you mean by a dblink, but what SQL permissions
do the Administrators have on each server? Are you sure the
BUILTIN/Administrators Windows group have the appropriate permissions
on the databases you want to select from?
>
Stu
>
>
traceable1 wrote:
I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).

I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.

The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.

Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.

I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.

Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.

I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.

I can connect via a dblink TO these new instances from the older boxes
fine.

I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.

Must be some sort of permissions problem, but I don't know what else to
check - - -

Please help!!

THANK YOU!!

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

databasemail setup for SQL 2005 Express

I have installed SQL 2005 Express with all options and turned on the database mail SP's in the surface area configuration, When I try to use database mail the entry in allitems is created but it is never sent. I followed the troubleshooting guides and find that databasemail90.exe was never installed in the binn folder. How can I get this file and whatever else might be missing to make this functionality work?Database Mail is not supported on SQL 2005 Express Edition.

Database won't update. Just Installed SQL Server. Please Help

I just installed SQL Server 2005 Express Edition to allow me to create databases in VB Express. The installation went fine (or so it seemed). When I complete the example to create a database and try to save the changes in the file, they are not retained.

I use the following statement to verify the changes have been made, but when I exit and return to the database, the changes are not made. If I make changes, the If statement correctly indicates the number of changes, but the are not saved. Any suggestions?

Dim RowsAffected As Integer = 0

RowsAffected = Me.CustomerTableAdapter1.Update(Me.MyCompanyDataSet1.Customer)

If RowsAffected > 0 Then

MessageBox.Show("Your updates were successful." & vbCrLf & _
RowsAffected.ToString & " row(s) were updated")

Else

MessageBox.Show("No changes were made.")

End If

Thanks...

Hi Patrick,

Check out my answer in this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=331048&SiteID=1.

You're hitting a common question related to running your application in Debug (F5) mode.

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

database usage

I have an application which uses a special login credential (username and
password) to access several sql databases.
Its installed on several clients. what's the best possible way to determine
what all databases the application connected to, at the end of the day from
SQL Server Side. ?
thxskg,
You did not tell us which interface are you using to connect to sql server.
In case you are using ADO or ADO.NET, you can setup the property "Applicatio
n
Name" in the connection string. Then you will be able to use sp_who2 or
sysprocesses and look for that value.
AMB
"skg" wrote:

> I have an application which uses a special login credential (username and
> password) to access several sql databases.
> Its installed on several clients. what's the best possible way to determin
e
> what all databases the application connected to, at the end of the day fro
m
> SQL Server Side. ?
> thx
>
>|||Thanks!!. I am using ado.net. The clients can close the application at the
end of the day.
In that case i will not be able to find out, which database.
What iam looking for is whethere there is a record whether a user logged in
a particular database today?
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> wrote in message
news:ED55575B-B66A-489A-8B3B-B2770446B696@.microsoft.com...
> skg,
> You did not tell us which interface are you using to connect to sql
> server.
> In case you are using ADO or ADO.NET, you can setup the property
> "Application
> Name" in the connection string. Then you will be able to use sp_who2 or
> sysprocesses and look for that value.
>
> AMB
> "skg" wrote:
>

Database Trouble

Hey if anybody can help me with this i will appreciate this....I Have Installed the MSDE database for the web Matrix however when i tried to establish connection in the web matrix it's tellling me that my connection is not available and I am unable to establish connection..If it helps I am on chapter 8 In the book of Begining Dynamic Websites w/Asp.net written by david sussman...Thank in advance.Did you follow the instructions onInstalling MSDE for ASP.NET Web Matrix?

How are you trying to establish a connection. through the Web Matrix Data window? Or through code?

Are you trying to connect via Windows authentication, or SQL Server authentication?

What is the exact error message?

Terri|||sorry for a late reply I could never find these posts after i put them up. Well I tried using the disk that comes along witht the book. I then uninstalled the software becuase of a possible computer problem. I then tried to re-install it. the disk runs the software and then displays a error invlaid message. Also due to this will my program tak e effect. Meaning will some of them not appear due to the .NETframework error?