I am attempting to install the MS SQL Server Desktop Engine. I have the
MSDE2000A.exe file and it unpacks successfully. I then run the setup and get
an install fail with the following:
Install message:
Setup failed to configure the server. See the server error logs and setup
error logs.
The only server error log I can find sez the following:
2005-02-11 14:09:52.11 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
server Copyright (C) 1988-2002 Microsoft Corporation.
server All rights reserved.
server Server Process ID is 2716.
server Logging SQL Server messages in file 'C:\Program Files\Microsoft
SQL Server\MSSQL\LOG\ERRORLOG'.
server SQL Server is starting at priority class 'normal'(1 CPU detected).
server SQL Server configured for thread mode processing.
server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
Owner Blocks.
spid3 Warning ******************
spid3 SQL Server started in single user mode. Updates allowed to system
catalogs.
spid3 Starting up database 'master'.
server Using 'SSNETLIB.DLL' version '8.0.766'.
spid5 Starting up database 'model'.
spid3 Server name is 'BART9550'.
spid3 Skipping startup of clean database id 5
spid3 Skipping startup of clean database id 6
spid3 Starting up database 'msdb'.
spid5 Clearing tempdb database.
server SQL server listening on Shared Memory.
server SQL Server is ready for client connections
spid5 Starting up database 'tempdb'.
spid3 Recovery complete.
spid3 SQL global counter collection task is created.
spid3 Warning: override, autoexec procedures skipped.
spid3 SQL Server is terminating due to 'stop' request from Service
Control Manager.
The application event log sez:
Event Type:Warning
Event Source:MSSQLServer
Event Category:(8)
Event ID:19011
Date:2/11/2005
Time:3:22:01 PM
User:N/A
Computer:BART9550
Description:
The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
(SpnRegister) : Error 1355.
Also another entry sez:
Event Type:Information
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:2/11/2005
Time:3:22:00 PM
User:N/A
Computer:BART9550
Description:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be able
to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: 17834,
Using 'SSNETLIB.DLL' version '8.0.766'.
How do I get this install to work as I have an application that requires SQL
desktop.
Thanks...
Read the readme files that come with MSDE. You can't just run the setup.exe
with no parameters an expect to install SQL Server exactly like you would
like it configured. MSDE a developer's tool so act like a developer and do
some investigative work before trying to install it.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:555AF044-A697-401C-8D08-0121BCFAFDD4@.microsoft.com...
>I am attempting to install the MS SQL Server Desktop Engine. I have the
> MSDE2000A.exe file and it unpacks successfully. I then run the setup and
> get
> an install fail with the following:
> Install message:
> Setup failed to configure the server. See the server error logs and setup
> error logs.
> The only server error log I can find sez the following:
> 2005-02-11 14:09:52.11 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
> server Copyright (C) 1988-2002 Microsoft Corporation.
> server All rights reserved.
> server Server Process ID is 2716.
> server Logging SQL Server messages in file 'C:\Program Files\Microsoft
> SQL Server\MSSQL\LOG\ERRORLOG'.
> server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> server SQL Server configured for thread mode processing.
> server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> spid3 Warning ******************
> spid3 SQL Server started in single user mode. Updates allowed to
> system
> catalogs.
> spid3 Starting up database 'master'.
> server Using 'SSNETLIB.DLL' version '8.0.766'.
> spid5 Starting up database 'model'.
> spid3 Server name is 'BART9550'.
> spid3 Skipping startup of clean database id 5
> spid3 Skipping startup of clean database id 6
> spid3 Starting up database 'msdb'.
> spid5 Clearing tempdb database.
> server SQL server listening on Shared Memory.
> server SQL Server is ready for client connections
> spid5 Starting up database 'tempdb'.
> spid3 Recovery complete.
> spid3 SQL global counter collection task is created.
> spid3 Warning: override, autoexec procedures skipped.
> spid3 SQL Server is terminating due to 'stop' request from Service
> Control Manager.
> The application event log sez:
> Event Type: Warning
> Event Source: MSSQLServer
> Event Category: (8)
> Event ID: 19011
> Date: 2/11/2005
> Time: 3:22:01 PM
> User: N/A
> Computer: BART9550
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be
> found. The local computer may not have the necessary registry information
> or
> message DLL files to display messages from a remote computer. You may be
> able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> (SpnRegister) : Error 1355.
>
> Also another entry sez:
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 2/11/2005
> Time: 3:22:00 PM
> User: N/A
> Computer: BART9550
> Description:
> The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
> found. The local computer may not have the necessary registry information
> or
> message DLL files to display messages from a remote computer. You may be
> able
> to use the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for details. The following information is part of the event:
> 17834,
> Using 'SSNETLIB.DLL' version '8.0.766'.
> How do I get this install to work as I have an application that requires
> SQL
> desktop.
> Thanks...
|||Hi Jim,
Thanks for the put down. Most appreciated.
I am not a developer. I am simply a computer user trying to use a program
that requires MSDE. And, I did not think that MSDE was a developer tool,
but simply a db engine that apps could plug into. But clearly you know more
than I.
And, with a little research by this end user I switched on no back out so I
could read the install log, and I supplied the setup.ini file with the
following:
BLANKSAPWD=1
SQLSecurityMode=SQL
By stopping the back out I now have SQL server running. but can not install
ODB connectivity drivers. ODBC 2.8 install was attempted in safemode.
Thanks Jim,...
Looking forward to your next put down.
BTW, I was directed to this forum by MS support as the place to receive help.
"Jim Young" wrote:
> Read the readme files that come with MSDE. You can't just run the setup.exe
> with no parameters an expect to install SQL Server exactly like you would
> like it configured. MSDE a developer's tool so act like a developer and do
> some investigative work before trying to install it.
> Jim
|||I'm sorry, my comment was most inappropriate. I'll try to help you with your
problem any way that I can.
If MSDE is running then MDAC (and the ODBC drivers) must already be
installed - SQL Server can't run without it.
I find it surprising and disappointing that the application you are trying
to install, that requires MSDE, does not make the installation of MSDE
seamless to you. What is the name of the program you are trying to install?
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:931E2080-068B-4120-BCC8-5F548C5C5B79@.microsoft.com...
> Hi Jim,
> Thanks for the put down. Most appreciated.
> I am not a developer. I am simply a computer user trying to use a program
> that requires MSDE. And, I did not think that MSDE was a developer tool,
> but simply a db engine that apps could plug into. But clearly you know
> more
> than I.
> And, with a little research by this end user I switched on no back out so
> I
> could read the install log, and I supplied the setup.ini file with the
> following:
> BLANKSAPWD=1
> SQLSecurityMode=SQL
> By stopping the back out I now have SQL server running. but can not
> install
> ODB connectivity drivers. ODBC 2.8 install was attempted in safemode.
> Thanks Jim,...
> Looking forward to your next put down.
> BTW, I was directed to this forum by MS support as the place to receive
> help.
> "Jim Young" wrote:
>
|||"Jim Young" wrote:
> I'm sorry, my comment was most inappropriate. I'll try to help you with your
> problem any way that I can.
> If MSDE is running then MDAC (and the ODBC drivers) must already be
> installed - SQL Server can't run without it.
> I find it surprising and disappointing that the application you are trying
> to install, that requires MSDE, does not make the installation of MSDE
> seamless to you. What is the name of the program you are trying to install?
Hi Jim,
Thank you. We’ll start fresh. Here’s the deal.
OS= WinXPpro.
App=ACT! 2005 (version7)
And yes, I have gone around and around with BEST software (makers of ACT!)
about the need to support the install of SQL MSDE. They claim that it is a
MS problem. However, I have used this install of XP for 2 or 3 yrs with
hardly a BSOD or any other problem. 70 or 80 programs run just fine. (Of
course not all at once). FYI ACT! Is a contact manager. I have been using
v6 with a great deal of success. However, v7 is a total rewrite and uses
SQL. It is essentially version one. I don’t know that I want to trust my
data to a program that is such a problem to install, and relies on some
else’s db engine.
On to the problem:
I could only get MSDE up and running when I switched on don’t back out on
failure:
setup.exe DISABLEROLLBACK=1
I did this based on a clue that the last line in the SQL error log was:
SQL Server is terminating due to a ‘stop’ request from Service Control
Manager.
My thought was that if it can be stopped it must be running. Lo and behold
on reboot the little computer icon is in the system tray. And Task list
shows SQL server running, and sqlmangr running.
However, the drivers tab in ODBC do NOT show SQL Server. And, when I
attempt to install MDAC v2.8 it bombs out.
Part of my problem is that I don’t under stand the functional relationships
between all these elements. My thought is that SQL MSDE is the db engine,
and that MDAC drivers in the ODBC are essentally middle ware allowing the
application to access the db.
Before SQL was running, when I last attempted to install ACT! v7 the error
out was 1603 can not configure server. I have not tried to reinstall yet
wanting to get as many ducks in a row as possible.
Looking forward to your post.
Thanks
BartC
|||You're correct MSDE is the database engine, MDAC is the communication layer
between the application and the database.
The DISABLEROLLBACK option is an option for the Windows installer to not
rollback any changes to your system if the installation fails. The original
error your received, 1603, is basically a general error reporting back that
the MSDE installation failed.
It seem to me that although MSDE is apparently running, the installation is
in an inconsistent state. What I would recommend is completely unistalling
MSDE. The following link is to a KB article for manually removing MSDE from
your system.
http://support.microsoft.com/default...b;en-us;320873
On your system go to Control Panel | Add Remove Program and see if there is
an entry for removing MSDE (it may be referenced as SQL Server). If you find
it then uninstall it. If that is successful then continue with the Remove
Files and Folders part of the KB article and finish the rest of the steps on
the article, removing registry entries.
If this is all successful then you have a system that is cleaned of MSDE.
Next I would try installing MDAC 2.8 and see if you get through that
successfully. If you don't then I would not attempt to install MSDE, since I
doubt it will succeed.
Next reinstall MSDE by running setup.exe with the following command line
parameters. You could use an .ini file for the SECURITYMODE or BLANKSAPWD
options if you want. Personally, I find using the command line easier.
/Lv c:\MSDEsetup.log SECURITYMODE="SQL" BLANKSAPWD=1
This will install a default instance of MSDE to the default directories
(c:\program files\Microsoft SQL Server) with a blank sa password.
If the install fails then you should have a verbose log on the root of drive
C. Post to this group the tail end of the log where the installation start
to break down; you'll see where there is first a failure and then rollbacks
of registry entries and files.
A lot embedded database application are moving their data storage over to
MSDE. It's a very powerful and reliable environment (once you get it
installed!). The problem is that SQL Server is much more complex of an
application to install than a simple flat file database or an Access based
solution. When the installation of MSDE goes sideways, recovering from it
can be quite a lot of trouble, as you've experienced.
Good luck - I hope you are able to get MSDE finally installed.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:1D534BF8-4C6F-49D9-A7F8-CB426F7A8EE8@.microsoft.com...
> "Jim Young" wrote:
> Hi Jim,
> Thank you. We'll start fresh. Here's the deal.
> OS= WinXPpro.
> App=ACT! 2005 (version7)
> And yes, I have gone around and around with BEST software (makers of ACT!)
> about the need to support the install of SQL MSDE. They claim that it is
> a
> MS problem. However, I have used this install of XP for 2 or 3 yrs with
> hardly a BSOD or any other problem. 70 or 80 programs run just fine. (Of
> course not all at once). FYI ACT! Is a contact manager. I have been
> using
> v6 with a great deal of success. However, v7 is a total rewrite and uses
> SQL. It is essentially version one. I don't know that I want to trust my
> data to a program that is such a problem to install, and relies on some
> else's db engine.
> On to the problem:
> I could only get MSDE up and running when I switched on don't back out on
> failure:
> setup.exe DISABLEROLLBACK=1
> I did this based on a clue that the last line in the SQL error log was:
> SQL Server is terminating due to a 'stop' request from Service Control
> Manager.
> My thought was that if it can be stopped it must be running. Lo and
> behold
> on reboot the little computer icon is in the system tray. And Task list
> shows SQL server running, and sqlmangr running.
> However, the drivers tab in ODBC do NOT show SQL Server. And, when I
> attempt to install MDAC v2.8 it bombs out.
> Part of my problem is that I don't under stand the functional
> relationships
> between all these elements. My thought is that SQL MSDE is the db engine,
> and that MDAC drivers in the ODBC are essentally middle ware allowing the
> application to access the db.
> Before SQL was running, when I last attempted to install ACT! v7 the error
> out was 1603 can not configure server. I have not tried to reinstall yet
> wanting to get as many ducks in a row as possible.
> Looking forward to your post.
> Thanks
> BartC
|||Hi Jim,
Well I see one error of my ways. I was installing MSDE first and then
attempting an install of MDAC 2.8.
If I understand you correctly after I remove everything I should start with
MDAC and then go on to installing MSDE.
I will try this, but it will have to wait for a day or two. The pressure of
work interfers with all the fun stuff ;-)
Thanks... I'll post results in a few days.
BartC
"Jim Young" wrote:
> snip...
> It seem to me that although MSDE is apparently running, the installation is
> in an inconsistent state. What I would recommend is completely unistalling
> MSDE. The following link is to a KB article for manually removing MSDE from
> your system.
|||It wasn't an error to install MDAC after MSDE; I just thought it would be a
good test to make sure that your system is in good order first. All windows
versions since Windows 2000 come with MDAC preinstalled, but it is best to
upgrade to 2.8 before you start the MSDE installation.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:075F0748-C889-4FA2-8E80-EE7482B059EE@.microsoft.com...
> Hi Jim,
> Well I see one error of my ways. I was installing MSDE first and then
> attempting an install of MDAC 2.8.
> If I understand you correctly after I remove everything I should start
> with
> MDAC and then go on to installing MSDE.
> I will try this, but it will have to wait for a day or two. The pressure
> of
> work interfers with all the fun stuff ;-)
> Thanks... I'll post results in a few days.
> BartC
>
>
>
> "Jim Young" wrote:
>
|||Jim,
OK, here is the latest:
re: KB 320873 - the Msizap.exe failed to find the SQL server to uninstall.
There was no SQL server in Add/Remove.
This in spite of the fact the icon was in the system tray, and I could call
up the control panel to start and stop the SQL server.
Soooooo... I stepped through the manual removal. And took out lots of SQL
keys that were in the registry, plus all the stuff that the KB article
suggested. Removed the temp files and the entire branch of SQL server in the
directory structure.
I also ran Registry First Aid and did a general clean up of the registry.
I then ran the MDACsetup and received the following:
MDAC 2.8 RTM is incompatible with this version of Windows. All of its
features are currently part of Windows.
There is a Details button that brought up nothing.
OK, so which is it... Incompatible with WinXP pro or already installed?
Hard to know from that error mess.
Forging ahead I ran the SQL setup with your (Jim’s) command line switches.
(See previous message.) That resulted in the same error as before... to wit:
Setup failed to configure the server. Refer to the error logs.
With the verbose log switched turned on the resultant log is 3.6 MB. I am
not going to post that (don’t think I could anyway.) There is a lot of note
1: 2360- stuff near the top, and then tons of opening and adding RegValues.
But here is the middle part. This is near the end of the install and a bit
into the rollback. It seems to vomit at (24!1C) at the config server
execution.
I am at a total loss as how to proceed.
Starting custom action CallSQLAdHlp
c:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
MSI (s) (24:B8) [06:36:45:799]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:799]: Executing op:
CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:36:45:809]: Executing op:
CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
MSI (s) (24:E8) [06:36:45:819]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI45.tmp, Entrypoint: InstallSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity succeeded
MSI (s) (24:B8) [06:36:46:070]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (24:B8) [06:36:46:070]: Executing op:
CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
MSI (s) (24:1C) [06:36:46:070]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI46.tmp, Entrypoint: SkuIt
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
MSI (s) (24:B8) [06:36:46:320]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (24:B8) [06:36:46:330]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (24:84) [06:36:46:330]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI47.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "c:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
MSI (c) (20:88) [06:37:12:798]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (s) (24!1C) [06:37:50:753]: Product: Microsoft SQL Server Desktop Engine
-- Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 6:37:50: InstallFinalize. Return value 3.
MSI (s) (24:B8) [06:37:50:783]: User policy value 'DisableRollback' is 0
MSI (s) (24:B8) [06:37:50:783]: Machine policy value 'DisableRollback' is 0
MSI (s) (24:B8) [06:37:50:823]: Executing op:
Header(Signature=1397708873,Version=300,Timestamp= 844313717,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
MSI (s) (24:B8) [06:37:50:823]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing backup files,CleanupTemplate=File: [1])
MSI (s) (24:B8) [06:37:50:823]: Executing op:
RegisterBackupFile(File=c:\Config.Msi\3cca84.rbf)
MSI (s) (24:B8) [06:37:50:823]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (24:B8) [06:37:50:823]: Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:50:833]: Executing op:
CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (24:F8) [06:37:50:833]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI48.tmp, Entrypoint: UnInstSQLAgentSecurity
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action UnInstSQLAgentSecurity
Starting custom action UnInstSQLAgentSecurity
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ActionStart(Name=InstallServices,Description=Insta lling new
services,Template=Service: [2])
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ServiceControl(,Name=MSSQLSERVER,Action=8,,)
MSI (s) (24:B8) [06:37:51:003]: Executing op:
ServiceControl(,Name=SQLSERVERAGENT,Action=8,,)
MSI (s) (24:B8) [06:37:51:193]: Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Registering type
libraries,Template=LibID: [1])
MSI (s) (24:B8) [06:37:51:193]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\WINDOWS\system 32\atl.dll,LibID={44EC0535-400F-11D0-9DCD-00A0C90391D3},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:193]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:203]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
MSI (s) (24:B8) [06:37:51:213]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:213]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:223]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
MSI (s) (24:B8) [06:37:51:233]: Executing op:
TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (24:B8) [06:37:51:233]: CMsiServices::ProcessTypeLibrary runs in
local context, not impersonated.
MSI (s) (24:B8) [06:37:51:304]: ProcessTypeLibraryCore returns: 0. (0 means
OK)
|||This may be a long shot, but is the Server service running on your machine?
Go to Control Panel | Adminstrative Tools | Services. If it is not running
then bring up the properties for the service, set the startup to automatic
and start the service. Then try re-installing MSDE.
Jim
"BartC" <BartC@.discussions.microsoft.com> wrote in message
news:B7EE12E7-D84E-4D83-96E6-70229C1F445C@.microsoft.com...
> Jim,
> OK, here is the latest:
> re: KB 320873 - the Msizap.exe failed to find the SQL server to uninstall.
> There was no SQL server in Add/Remove.
> This in spite of the fact the icon was in the system tray, and I could
> call
> up the control panel to start and stop the SQL server.
> Soooooo... I stepped through the manual removal. And took out lots of
> SQL
> keys that were in the registry, plus all the stuff that the KB article
> suggested. Removed the temp files and the entire branch of SQL server in
> the
> directory structure.
> I also ran Registry First Aid and did a general clean up of the registry.
> I then ran the MDACsetup and received the following:
> MDAC 2.8 RTM is incompatible with this version of Windows. All of its
> features are currently part of Windows.
> There is a Details button that brought up nothing.
> OK, so which is it... Incompatible with WinXP pro or already installed?
> Hard to know from that error mess.
> Forging ahead I ran the SQL setup with your (Jim's) command line switches.
> (See previous message.) That resulted in the same error as before... to
> wit:
> Setup failed to configure the server. Refer to the error logs.
> With the verbose log switched turned on the resultant log is 3.6 MB. I am
> not going to post that (don't think I could anyway.) There is a lot of
> note
> 1: 2360- stuff near the top, and then tons of opening and adding
> RegValues.
> But here is the middle part. This is near the end of the install and a
> bit
> into the rollback. It seems to vomit at (24!1C) at the config server
> execution.
> I am at a total loss as how to proceed.
> Starting custom action CallSQLAdHlp
> c:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
> MSI (s) (24:B8) [06:36:45:799]: Executing op:
> ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:36:45:799]: Executing op:
> CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
> MSI (s) (24:B8) [06:36:45:809]: Executing op:
> ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:36:45:809]: Executing op:
> CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
> MSI (s) (24:E8) [06:36:45:819]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI45.tmp, Entrypoint: InstallSQLAgentSecurity
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity succeeded
> MSI (s) (24:B8) [06:36:46:070]: Executing op:
> ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
> MSI (s) (24:B8) [06:36:46:070]: Executing op:
> CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
> MSI (s) (24:1C) [06:36:46:070]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI46.tmp, Entrypoint: SkuIt
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action SkuIt
> MSI (s) (24:B8) [06:36:46:320]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (24:B8) [06:36:46:330]: Executing op:
> CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
> MSI (s) (24:84) [06:36:46:330]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI47.tmp, Entrypoint: ConfigServer
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action ConfigServer
> Executing "c:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
> -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
> MSI (c) (20:88) [06:37:12:798]: Font created. Charset: Req=0, Ret=0,
> Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> MSI (s) (24!1C) [06:37:50:753]: Product: Microsoft SQL Server Desktop
> Engine
> -- Setup failed to configure the server. Refer to the server error logs
> and
> setup error logs for more information.
> Action ended 6:37:50: InstallFinalize. Return value 3.
> MSI (s) (24:B8) [06:37:50:783]: User policy value 'DisableRollback' is 0
> MSI (s) (24:B8) [06:37:50:783]: Machine policy value 'DisableRollback' is
> 0
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> Header(Signature=1397708873,Version=300,Timestamp= 844313717,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> DialogInfo(Type=0,Argument=1033)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
> action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing
> backup files,CleanupTemplate=File: [1])
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> RegisterBackupFile(File=c:\Config.Msi\3cca84.rbf)
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (24:B8) [06:37:50:823]: Executing op:
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
> SQL Server Desktop
> Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:50:833]: Executing op:
> CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
> MSI (s) (24:F8) [06:37:50:833]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI48.tmp, Entrypoint: UnInstSQLAgentSecurity
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Bart\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action UnInstSQLAgentSecurity
> Starting custom action UnInstSQLAgentSecurity
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ActionStart(Name=InstallServices,Description=Insta lling new
> services,Template=Service: [2])
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ServiceControl(,Name=MSSQLSERVER,Action=8,,)
> MSI (s) (24:B8) [06:37:51:003]: Executing op:
> ServiceControl(,Name=SQLSERVERAGENT,Action=8,,)
> MSI (s) (24:B8) [06:37:51:193]: Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Registering type
> libraries,Template=LibID: [1])
> MSI (s) (24:B8) [06:37:51:193]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\WINDOWS\system 32\atl.dll,LibID={44EC0535-400F-11D0-9DCD-00A0C90391D3},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:193]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:203]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
> MSI (s) (24:B8) [06:37:51:213]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:213]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:223]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
> MSI (s) (24:B8) [06:37:51:233]: Executing op:
> TypeLibraryUnregister(,,FilePath=c:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5},Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (24:B8) [06:37:51:233]: CMsiServices::ProcessTypeLibrary runs in
> local context, not impersonated.
> MSI (s) (24:B8) [06:37:51:304]: ProcessTypeLibraryCore returns: 0. (0
> means
> OK)
>
Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts
Thursday, March 29, 2012
Tuesday, March 27, 2012
can not install MSDE
Hi
I have installed .net framework 1.1 and .net web matrix from 'sams teach yourself asp.net' CD. I installed MSDE from the same CD, its not giving any error, but at the end it does not promt to restart the computer, even after restarting I can not see the MSDE icon in the system tray, also I dont see MSDE in the add/remove programs in control panel.I installed sql2kdesksp3.exe from www.asp.net/msde/, but the same thing repeats.
I have installed .net framework 1.1 and .net web matrix from 'sams teach yourself asp.net' CD. I installed MSDE from the same CD, its not giving any error, but at the end it does not promt to restart the computer, even after restarting I can not see the MSDE icon in the system tray, also I dont see MSDE in the add/remove programs in control panel.I installed sql2kdesksp3.exe from www.asp.net/msde/, but the same thing repeats.
1. Shld I install the sql2kasp3.exe(Analysis services companents) and sql2ksp3.exe(Databasre components) also?
I am new to asp,It will be helpful if somebody can tell me how to install MSDE.
ThanksHere are step-by-step instructions. Try going over them again in case the machine didn't install it properly:
http://www.asp.net/webmatrix/guidedtour/Appendices/installMsde.aspx|||Hii
I Installed MSDE via command line as given in tht site and there was no error but dint get tht MSDE icon in system tray.
I tried to install MSDE via batch file, there was no error, but when started the MSDE service, I couldnt see the "MSSQLSERVER", there is only MSSQLServiceASHelper, when clicked on it it gives the error as
"could not start the MSSQLServerADHelper service on Local Computer
eror2:The system cannot find the file specified"
Now wht shld I do??Can I download the missing file separately.I installed from the cd again and the same repeated.plzz tell me whtt I shld do now.
Thank You|||Yeah, follow the directions here to reinstall:
http://www.asp.net/msde/default.aspx?tabindex=0&tabid=1|||Hi
I tried by installing from tht site, to install it again it takes another 8 to 10hours as I use dialup connection.Cant I download the missing file separately?|||The files you point to are Service Pack 3 files for SQL Server 2000. You need this file to patch MSDE with SP3: Sql2kdesksp3.exe
Check out the SQL Server and MSDE Service Pack 3a update page:
http://www.microsoft.com/sql/downloads/2000/SP3.asp
You may be able to order on CD, or at least download the correct file.|||Thanks a lot for answering me, I am downloading it again from the given site, if the same problem repeates then I'll buy the Cd.
Does SQL server 2000 and MSDE work the same way?
Thank you.|||Pretty much. MSDE doesn't have all the high-end features that SQL Server has, nor does it have a graphical interface designer like Query Analyzer or Enterprise Manager.
Thursday, March 22, 2012
Can not connect to MSDE 2000 through my PDA application
Hi, I am new to MSDE and am having a problem connecting to it through my PDA
application. Everytime i try to open the connection i get a exception of
PlatformNotSupportedException.
I have checked this problem for many times and fail to find an ideal
solution. My question is whether it was caused by an low version of MSDE? I
have tried to update the MSDE with SP4, but it failed. The error message is
:The instance name specified is invalid.
Anyone can help me ? Thanks!
hi,
phil wrote:
> Hi, I am new to MSDE and am having a problem connecting to it through
> my PDA application. Everytime i try to open the connection i get a
> exception of PlatformNotSupportedException.
> I have checked this problem for many times and fail to find an ideal
> solution. My question is whether it was caused by an low version of
> MSDE? I have tried to update the MSDE with SP4, but it failed. The
> error message is
> Anyone can help me ? Thanks!
I recently wote a little 300k PocketPC app using Vb.Net and the Compact
Framework for our inhouse order entry management... it is a connected app,
as it works connected via wi-fi with the main SQL Server engine... and it
works great :D
I think you've better ask in the specific compiler/language ng for better
luck...
as regard the MSDE upgrade to sp4, I've found that the instance name is
better understood by the setup.exe boostrap installer if provided without
quotes, in the form
c:\...\>setup.exe /upgradesp SQLRUN INSTANCENAME=whatever ..(other params)
/L*v "c:\MsdeSP4.txt"
but this is my own experience...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi Andrea Montanari, thanks for ur reply. As to the installation of SP4, i
have solved the problem with ur great suggestion. Thanks again.
But i still sufferd the problem with my pda app to connect with a MSDE
DATABSE. When I'd like to use SqlConnection.Open() in a Pocket PC 2002
application, I get an error message - PlatformNotSupportedException. I've
tryed it on Windows CE Emulator and my PDA Device, but the result was the
same.
There is my code snippet:
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim cn As New System.Data.SqlClient.SqlConnection("User
ID=sa;password=sa;database=Test;server=192.168.1.5 ")
cn.Open()
Catch exSQL As SqlException
Dim errSQL As SqlError
For Each errSQL In exSQL.Errors
MessageBox.Show(errSQL.Message)
Next
Catch ex1 As Exception
MessageBox.Show(ex1.Message)
Finally
MessageBox.Show("test fail")
End Sub
When i try to build a windows application project with this code, it works
well, Can anybody give me a tip, how can i solve the problem?
Thank's in advance.
Operating system: Windows XP professional + sp2
Development Tool: Visual Studion 2003
Database: MSDE 2000 Release A
PDA device: iPaq H3870, Windows CE 4.1
|||hi,
phil wrote:
> hi Andrea Montanari, thanks for ur reply. As to the installation of
> SP4, i have solved the problem with ur great suggestion. Thanks again.
> But i still sufferd the problem with my pda app to connect with a MSDE
> DATABSE. When I'd like to use SqlConnection.Open() in a Pocket PC 2002
> application, I get an error message - PlatformNotSupportedException.
> I've tryed it on Windows CE Emulator and my PDA Device, but the
> result was the same.
>
> There is my code snippet:
> Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> System.EventArgs) Handles Button1.Click
> Dim cn As New System.Data.SqlClient.SqlConnection("User
> ID=sa;password=sa;database=Test;server=192.168.1.5 ")
>
it seems fine, to me... but unfortunately have no further hints.. try in the
DotNet compact framework ngs...
sorry..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You need to use the System.Data.SqlServerCe namespace and make sure you are
not referencing anything in then 1.1 framework. All references need to be
to the compact framework
http://msdn.microsoft.com/library/de...qlserverce.asp
In c#
SqlCeConnection conn = new SqlCeConnection( connString );
conn.Open();
"phil" <phil@.discussions.microsoft.com> wrote in message
news:02E40A6C-48C3-4DAD-9EDB-3F7B76CFA027@.microsoft.com...
> hi Andrea Montanari, thanks for ur reply. As to the installation of SP4, i
> have solved the problem with ur great suggestion. Thanks again.
> But i still sufferd the problem with my pda app to connect with a MSDE
> DATABSE. When I'd like to use SqlConnection.Open() in a Pocket PC 2002
> application, I get an error message - PlatformNotSupportedException. I've
> tryed it on Windows CE Emulator and my PDA Device, but the result was the
> same.
>
> There is my code snippet:
> Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> System.EventArgs) Handles Button1.Click
> Dim cn As New System.Data.SqlClient.SqlConnection("User
> ID=sa;password=sa;database=Test;server=192.168.1.5 ")
> cn.Open()
> Catch exSQL As SqlException
> Dim errSQL As SqlError
> For Each errSQL In exSQL.Errors
> MessageBox.Show(errSQL.Message)
> Next
> Catch ex1 As Exception
> MessageBox.Show(ex1.Message)
> Finally
> MessageBox.Show("test fail")
> End Sub
> When i try to build a windows application project with this code, it
works
> well, Can anybody give me a tip, how can i solve the problem?
> Thank's in advance.
>
> Operating system: Windows XP professional + sp2
> Development Tool: Visual Studion 2003
> Database: MSDE 2000 Release A
> PDA device: iPaq H3870, Windows CE 4.1
>
|||hi Darren
Darren wrote:
> You need to use the System.Data.SqlServerCe namespace and make sure
> you are not referencing anything in then 1.1 framework. All
> references need to be to the compact framework
> http://msdn.microsoft.com/library/de...qlserverce.asp
> In c#
> SqlCeConnection conn = new SqlCeConnection( connString );
> conn.Open();
>
this is true for a SQLCe connection, but not for a connection to a
"standard" SQL Server/MSDE remote instance via wi-fi..
in this case, the System.Data.SqlClient reference is needed as already
indicated by Phil...
and the compact framework includes SqlClient component...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for the info.
I didn't realize that namespace was available in the CF.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3k2698Fs76uvU1@.individual.net...[vbcol=seagreen]
> hi Darren
> Darren wrote:
http://msdn.microsoft.com/library/de...qlserverce.asp
> this is true for a SQLCe connection, but not for a connection to a
> "standard" SQL Server/MSDE remote instance via wi-fi..
> in this case, the System.Data.SqlClient reference is needed as already
> indicated by Phil...
> and the compact framework includes SqlClient component...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
application. Everytime i try to open the connection i get a exception of
PlatformNotSupportedException.
I have checked this problem for many times and fail to find an ideal
solution. My question is whether it was caused by an low version of MSDE? I
have tried to update the MSDE with SP4, but it failed. The error message is
:The instance name specified is invalid.
Anyone can help me ? Thanks!
hi,
phil wrote:
> Hi, I am new to MSDE and am having a problem connecting to it through
> my PDA application. Everytime i try to open the connection i get a
> exception of PlatformNotSupportedException.
> I have checked this problem for many times and fail to find an ideal
> solution. My question is whether it was caused by an low version of
> MSDE? I have tried to update the MSDE with SP4, but it failed. The
> error message is
> Anyone can help me ? Thanks!
I recently wote a little 300k PocketPC app using Vb.Net and the Compact
Framework for our inhouse order entry management... it is a connected app,
as it works connected via wi-fi with the main SQL Server engine... and it
works great :D
I think you've better ask in the specific compiler/language ng for better
luck...
as regard the MSDE upgrade to sp4, I've found that the instance name is
better understood by the setup.exe boostrap installer if provided without
quotes, in the form
c:\...\>setup.exe /upgradesp SQLRUN INSTANCENAME=whatever ..(other params)
/L*v "c:\MsdeSP4.txt"
but this is my own experience...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi Andrea Montanari, thanks for ur reply. As to the installation of SP4, i
have solved the problem with ur great suggestion. Thanks again.
But i still sufferd the problem with my pda app to connect with a MSDE
DATABSE. When I'd like to use SqlConnection.Open() in a Pocket PC 2002
application, I get an error message - PlatformNotSupportedException. I've
tryed it on Windows CE Emulator and my PDA Device, but the result was the
same.
There is my code snippet:
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim cn As New System.Data.SqlClient.SqlConnection("User
ID=sa;password=sa;database=Test;server=192.168.1.5 ")
cn.Open()
Catch exSQL As SqlException
Dim errSQL As SqlError
For Each errSQL In exSQL.Errors
MessageBox.Show(errSQL.Message)
Next
Catch ex1 As Exception
MessageBox.Show(ex1.Message)
Finally
MessageBox.Show("test fail")
End Sub
When i try to build a windows application project with this code, it works
well, Can anybody give me a tip, how can i solve the problem?
Thank's in advance.
Operating system: Windows XP professional + sp2
Development Tool: Visual Studion 2003
Database: MSDE 2000 Release A
PDA device: iPaq H3870, Windows CE 4.1
|||hi,
phil wrote:
> hi Andrea Montanari, thanks for ur reply. As to the installation of
> SP4, i have solved the problem with ur great suggestion. Thanks again.
> But i still sufferd the problem with my pda app to connect with a MSDE
> DATABSE. When I'd like to use SqlConnection.Open() in a Pocket PC 2002
> application, I get an error message - PlatformNotSupportedException.
> I've tryed it on Windows CE Emulator and my PDA Device, but the
> result was the same.
>
> There is my code snippet:
> Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> System.EventArgs) Handles Button1.Click
> Dim cn As New System.Data.SqlClient.SqlConnection("User
> ID=sa;password=sa;database=Test;server=192.168.1.5 ")
>
it seems fine, to me... but unfortunately have no further hints.. try in the
DotNet compact framework ngs...
sorry..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You need to use the System.Data.SqlServerCe namespace and make sure you are
not referencing anything in then 1.1 framework. All references need to be
to the compact framework
http://msdn.microsoft.com/library/de...qlserverce.asp
In c#
SqlCeConnection conn = new SqlCeConnection( connString );
conn.Open();
"phil" <phil@.discussions.microsoft.com> wrote in message
news:02E40A6C-48C3-4DAD-9EDB-3F7B76CFA027@.microsoft.com...
> hi Andrea Montanari, thanks for ur reply. As to the installation of SP4, i
> have solved the problem with ur great suggestion. Thanks again.
> But i still sufferd the problem with my pda app to connect with a MSDE
> DATABSE. When I'd like to use SqlConnection.Open() in a Pocket PC 2002
> application, I get an error message - PlatformNotSupportedException. I've
> tryed it on Windows CE Emulator and my PDA Device, but the result was the
> same.
>
> There is my code snippet:
> Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
> System.EventArgs) Handles Button1.Click
> Dim cn As New System.Data.SqlClient.SqlConnection("User
> ID=sa;password=sa;database=Test;server=192.168.1.5 ")
> cn.Open()
> Catch exSQL As SqlException
> Dim errSQL As SqlError
> For Each errSQL In exSQL.Errors
> MessageBox.Show(errSQL.Message)
> Next
> Catch ex1 As Exception
> MessageBox.Show(ex1.Message)
> Finally
> MessageBox.Show("test fail")
> End Sub
> When i try to build a windows application project with this code, it
works
> well, Can anybody give me a tip, how can i solve the problem?
> Thank's in advance.
>
> Operating system: Windows XP professional + sp2
> Development Tool: Visual Studion 2003
> Database: MSDE 2000 Release A
> PDA device: iPaq H3870, Windows CE 4.1
>
|||hi Darren
Darren wrote:
> You need to use the System.Data.SqlServerCe namespace and make sure
> you are not referencing anything in then 1.1 framework. All
> references need to be to the compact framework
> http://msdn.microsoft.com/library/de...qlserverce.asp
> In c#
> SqlCeConnection conn = new SqlCeConnection( connString );
> conn.Open();
>
this is true for a SQLCe connection, but not for a connection to a
"standard" SQL Server/MSDE remote instance via wi-fi..
in this case, the System.Data.SqlClient reference is needed as already
indicated by Phil...
and the compact framework includes SqlClient component...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for the info.
I didn't realize that namespace was available in the CF.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3k2698Fs76uvU1@.individual.net...[vbcol=seagreen]
> hi Darren
> Darren wrote:
http://msdn.microsoft.com/library/de...qlserverce.asp
> this is true for a SQLCe connection, but not for a connection to a
> "standard" SQL Server/MSDE remote instance via wi-fi..
> in this case, the System.Data.SqlClient reference is needed as already
> indicated by Phil...
> and the compact framework includes SqlClient component...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Tuesday, March 20, 2012
Can not conenct to MSDE with VB.NET 2003
Hellow
First i appoligize for my english but I'm from Belgium
Second, this is my problem:
I installed a Server on my Server PC (Windows XP Professional)
setup SAPWD="mypwd" INSTANCENAME="MSDESERVER" DISABLENETWORKPROTOCOLS=0
SECURITYMODE="SQL" TARGETDIR="C:\MSDEINSTALL" /L*v C:\MSDELOG.TXT +
Enter
Works perfect, then I attached a database to it
osql -E -S peter-developer\VA3+ ENTER
EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
@.filename2='C:\test\VA2005_LOG.ldf' + ENTER
This works, and in vb.net i can connect to it with
"Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
Security=SSPI;"
But when i try this from i remote PC (Windows XP) I get an error that
says: SQL server does not exist or access is denied
I searched almost everywhere and i can't find the answer.
EXTRA information
With svrnetcn.exe a set Named pipes, TCP/IP and NWLINK IPX/SPX to
enabled
I put the firewall of, and the firewal of the router is off
Please help me
How do you connect the MSDE from the remote computer? Via an application
with the same ConnectionString as you showed? If yes, that means you are
using Windows security to connect to the MSDE. Is the remote computer on the
same domain network or peer-to-peer network? If it is domain network, you
need to have a SQL Server login created in MSDE that maps to the domain user
account used on that remote computer, or the user logged on to that remote
computer is a domain admin.
Since your MSDE's SQL Server security is enabled, you could specify user
name and password in the ConnectionString (i.e. using SQL Server security,
instead of Windows security). More important thing is to do a bit more study
on SQL Server/MSDE security.
"Thorgal" <declerck_peter@.yahoo.com> wrote in message
news:1164211363.096453.64060@.e3g2000cwe.googlegrou ps.com...
> Hellow
> First i appoligize for my english but I'm from Belgium
> Second, this is my problem:
> I installed a Server on my Server PC (Windows XP Professional)
> setup SAPWD="mypwd" INSTANCENAME="MSDESERVER" DISABLENETWORKPROTOCOLS=0
> SECURITYMODE="SQL" TARGETDIR="C:\MSDEINSTALL" /L*v C:\MSDELOG.TXT +
> Enter
> Works perfect, then I attached a database to it
> osql -E -S peter-developer\VA3+ ENTER
> EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
> @.filename2='C:\test\VA2005_LOG.ldf' + ENTER
> This works, and in vb.net i can connect to it with
> "Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
> Security=SSPI;"
> But when i try this from i remote PC (Windows XP) I get an error that
> says: SQL server does not exist or access is denied
> I searched almost everywhere and i can't find the answer.
> EXTRA information
> With svrnetcn.exe a set Named pipes, TCP/IP and NWLINK IPX/SPX to
> enabled
> I put the firewall of, and the firewal of the router is off
> Please help me
>
|||I'm confused.
In the setup, you indicate that the instance name is: "MSDESERVER", yet in
the connection string you are connecting to: "PETER-DEVELOPER\va3".
Do you have a second instance named [va3]?
Shouldn't you use the instancename [MSDESERVER] in the connection string if
you want to connect to that instance?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thorgal" <declerck_peter@.yahoo.com> wrote in message
news:1164211363.096453.64060@.e3g2000cwe.googlegrou ps.com...
> Hellow
> First i appoligize for my english but I'm from Belgium
> Second, this is my problem:
> I installed a Server on my Server PC (Windows XP Professional)
> setup SAPWD="mypwd" INSTANCENAME="MSDESERVER" DISABLENETWORKPROTOCOLS=0
> SECURITYMODE="SQL" TARGETDIR="C:\MSDEINSTALL" /L*v C:\MSDELOG.TXT +
> Enter
> Works perfect, then I attached a database to it
> osql -E -S peter-developer\VA3+ ENTER
> EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
> @.filename2='C:\test\VA2005_LOG.ldf' + ENTER
> This works, and in vb.net i can connect to it with
> "Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
> Security=SSPI;"
> But when i try this from i remote PC (Windows XP) I get an error that
> says: SQL server does not exist or access is denied
> I searched almost everywhere and i can't find the answer.
> EXTRA information
> With svrnetcn.exe a set Named pipes, TCP/IP and NWLINK IPX/SPX to
> enabled
> I put the firewall of, and the firewal of the router is off
> Please help me
>
|||Arnie Rowland schreef:
> I'm confused.
> In the setup, you indicate that the instance name is: "MSDESERVER", yet in
> the connection string you are connecting to: "PETER-DEVELOPER\va3".
> Do you have a second instance named [va3]?
> Shouldn't you use the instancename [MSDESERVER] in the connection string if
> you want to connect to that instance?
> --
Sorry i copy pasted somethings from the installation board but this is
how it is
setup SAPWD="mypwd" INSTANCENAME="VA3" DISABLENETWORKPROTOCOLS=0
SECURITYMODE="SQL" TARGETDIR="C:\VA3" /L*v C:\MSDELOG.TXT +
Enter
Then attaching the database:
osql -E -S peter-developer\VA3+ ENTER
EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
@.filename2='C:\test\VA2005_LOG.ldf' + ENTER
Sorry for that mistake.
The 2 computers are in the same worgroup, and when i typ
\\peter-developer I see the server PC and I can get files from it or
drop files on the PC.
I want to connect to the VA3 server with a VB.NET 2003 application and
i do it with following connection string
"Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
Security=SSPI;"
Doesn't work
"Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
Security=SSPI;User ID=sa; Password=pass"
Doesn't work
"Data Source=PETER-DEVELOPER\va3,1433;Initial Catalog=VA2005;Integrated
Security=SSPI;User ID=sa; Password=pass"
Doesn't work
"Data Source=Peter-developer\VA3,1433;Network
Library=DBMSSOCN;Integrated Security=SSPI;Initial Catalog=VA2005;User
ID=peter;Password=peter"
Doesn't work ether
You say something about making a new user, I don't understand that,
could you explain it again please
|||You do not need to combine both "Integrated Security=SSPI" AND "User ID=sa;
Password=pass".
It is EITHER "Integrated Security=SSPI" OR "User ID=sa; Password=pass".
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thorgal" <declerck_peter@.yahoo.com> wrote in message
news:1164269346.083379.243730@.l12g2000cwl.googlegr oups.com...
> Arnie Rowland schreef:
>
> Sorry i copy pasted somethings from the installation board but this is
> how it is
> setup SAPWD="mypwd" INSTANCENAME="VA3" DISABLENETWORKPROTOCOLS=0
>
> SECURITYMODE="SQL" TARGETDIR="C:\VA3" /L*v C:\MSDELOG.TXT +
> Enter
> Then attaching the database:
> osql -E -S peter-developer\VA3+ ENTER
> EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
> @.filename2='C:\test\VA2005_LOG.ldf' + ENTER
>
> Sorry for that mistake.
> The 2 computers are in the same worgroup, and when i typ
> \\peter-developer I see the server PC and I can get files from it or
> drop files on the PC.
> I want to connect to the VA3 server with a VB.NET 2003 application and
> i do it with following connection string
> "Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
> Security=SSPI;"
>
> Doesn't work
> "Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
> Security=SSPI;User ID=sa; Password=pass"
> Doesn't work
> "Data Source=PETER-DEVELOPER\va3,1433;Initial Catalog=VA2005;Integrated
> Security=SSPI;User ID=sa; Password=pass"
> Doesn't work
> "Data Source=Peter-developer\VA3,1433;Network
> Library=DBMSSOCN;Integrated Security=SSPI;Initial Catalog=VA2005;User
> ID=peter;Password=peter"
> Doesn't work ether
> You say something about making a new user, I don't understand that,
> could you explain it again please
>
sql
First i appoligize for my english but I'm from Belgium
Second, this is my problem:
I installed a Server on my Server PC (Windows XP Professional)
setup SAPWD="mypwd" INSTANCENAME="MSDESERVER" DISABLENETWORKPROTOCOLS=0
SECURITYMODE="SQL" TARGETDIR="C:\MSDEINSTALL" /L*v C:\MSDELOG.TXT +
Enter
Works perfect, then I attached a database to it
osql -E -S peter-developer\VA3+ ENTER
EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
@.filename2='C:\test\VA2005_LOG.ldf' + ENTER
This works, and in vb.net i can connect to it with
"Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
Security=SSPI;"
But when i try this from i remote PC (Windows XP) I get an error that
says: SQL server does not exist or access is denied
I searched almost everywhere and i can't find the answer.
EXTRA information
With svrnetcn.exe a set Named pipes, TCP/IP and NWLINK IPX/SPX to
enabled
I put the firewall of, and the firewal of the router is off
Please help me
How do you connect the MSDE from the remote computer? Via an application
with the same ConnectionString as you showed? If yes, that means you are
using Windows security to connect to the MSDE. Is the remote computer on the
same domain network or peer-to-peer network? If it is domain network, you
need to have a SQL Server login created in MSDE that maps to the domain user
account used on that remote computer, or the user logged on to that remote
computer is a domain admin.
Since your MSDE's SQL Server security is enabled, you could specify user
name and password in the ConnectionString (i.e. using SQL Server security,
instead of Windows security). More important thing is to do a bit more study
on SQL Server/MSDE security.
"Thorgal" <declerck_peter@.yahoo.com> wrote in message
news:1164211363.096453.64060@.e3g2000cwe.googlegrou ps.com...
> Hellow
> First i appoligize for my english but I'm from Belgium
> Second, this is my problem:
> I installed a Server on my Server PC (Windows XP Professional)
> setup SAPWD="mypwd" INSTANCENAME="MSDESERVER" DISABLENETWORKPROTOCOLS=0
> SECURITYMODE="SQL" TARGETDIR="C:\MSDEINSTALL" /L*v C:\MSDELOG.TXT +
> Enter
> Works perfect, then I attached a database to it
> osql -E -S peter-developer\VA3+ ENTER
> EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
> @.filename2='C:\test\VA2005_LOG.ldf' + ENTER
> This works, and in vb.net i can connect to it with
> "Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
> Security=SSPI;"
> But when i try this from i remote PC (Windows XP) I get an error that
> says: SQL server does not exist or access is denied
> I searched almost everywhere and i can't find the answer.
> EXTRA information
> With svrnetcn.exe a set Named pipes, TCP/IP and NWLINK IPX/SPX to
> enabled
> I put the firewall of, and the firewal of the router is off
> Please help me
>
|||I'm confused.
In the setup, you indicate that the instance name is: "MSDESERVER", yet in
the connection string you are connecting to: "PETER-DEVELOPER\va3".
Do you have a second instance named [va3]?
Shouldn't you use the instancename [MSDESERVER] in the connection string if
you want to connect to that instance?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thorgal" <declerck_peter@.yahoo.com> wrote in message
news:1164211363.096453.64060@.e3g2000cwe.googlegrou ps.com...
> Hellow
> First i appoligize for my english but I'm from Belgium
> Second, this is my problem:
> I installed a Server on my Server PC (Windows XP Professional)
> setup SAPWD="mypwd" INSTANCENAME="MSDESERVER" DISABLENETWORKPROTOCOLS=0
> SECURITYMODE="SQL" TARGETDIR="C:\MSDEINSTALL" /L*v C:\MSDELOG.TXT +
> Enter
> Works perfect, then I attached a database to it
> osql -E -S peter-developer\VA3+ ENTER
> EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
> @.filename2='C:\test\VA2005_LOG.ldf' + ENTER
> This works, and in vb.net i can connect to it with
> "Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
> Security=SSPI;"
> But when i try this from i remote PC (Windows XP) I get an error that
> says: SQL server does not exist or access is denied
> I searched almost everywhere and i can't find the answer.
> EXTRA information
> With svrnetcn.exe a set Named pipes, TCP/IP and NWLINK IPX/SPX to
> enabled
> I put the firewall of, and the firewal of the router is off
> Please help me
>
|||Arnie Rowland schreef:
> I'm confused.
> In the setup, you indicate that the instance name is: "MSDESERVER", yet in
> the connection string you are connecting to: "PETER-DEVELOPER\va3".
> Do you have a second instance named [va3]?
> Shouldn't you use the instancename [MSDESERVER] in the connection string if
> you want to connect to that instance?
> --
Sorry i copy pasted somethings from the installation board but this is
how it is
setup SAPWD="mypwd" INSTANCENAME="VA3" DISABLENETWORKPROTOCOLS=0
SECURITYMODE="SQL" TARGETDIR="C:\VA3" /L*v C:\MSDELOG.TXT +
Enter
Then attaching the database:
osql -E -S peter-developer\VA3+ ENTER
EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
@.filename2='C:\test\VA2005_LOG.ldf' + ENTER
Sorry for that mistake.
The 2 computers are in the same worgroup, and when i typ
\\peter-developer I see the server PC and I can get files from it or
drop files on the PC.
I want to connect to the VA3 server with a VB.NET 2003 application and
i do it with following connection string
"Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
Security=SSPI;"
Doesn't work
"Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
Security=SSPI;User ID=sa; Password=pass"
Doesn't work
"Data Source=PETER-DEVELOPER\va3,1433;Initial Catalog=VA2005;Integrated
Security=SSPI;User ID=sa; Password=pass"
Doesn't work
"Data Source=Peter-developer\VA3,1433;Network
Library=DBMSSOCN;Integrated Security=SSPI;Initial Catalog=VA2005;User
ID=peter;Password=peter"
Doesn't work ether
You say something about making a new user, I don't understand that,
could you explain it again please
|||You do not need to combine both "Integrated Security=SSPI" AND "User ID=sa;
Password=pass".
It is EITHER "Integrated Security=SSPI" OR "User ID=sa; Password=pass".
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Thorgal" <declerck_peter@.yahoo.com> wrote in message
news:1164269346.083379.243730@.l12g2000cwl.googlegr oups.com...
> Arnie Rowland schreef:
>
> Sorry i copy pasted somethings from the installation board but this is
> how it is
> setup SAPWD="mypwd" INSTANCENAME="VA3" DISABLENETWORKPROTOCOLS=0
>
> SECURITYMODE="SQL" TARGETDIR="C:\VA3" /L*v C:\MSDELOG.TXT +
> Enter
> Then attaching the database:
> osql -E -S peter-developer\VA3+ ENTER
> EXEC sp_attach_db @.dbname='VA2005',@.filename1='C:\test\VA2005.mdf',
> @.filename2='C:\test\VA2005_LOG.ldf' + ENTER
>
> Sorry for that mistake.
> The 2 computers are in the same worgroup, and when i typ
> \\peter-developer I see the server PC and I can get files from it or
> drop files on the PC.
> I want to connect to the VA3 server with a VB.NET 2003 application and
> i do it with following connection string
> "Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
> Security=SSPI;"
>
> Doesn't work
> "Data Source=PETER-DEVELOPER\va3;Initial Catalog=VA2005;Integrated
> Security=SSPI;User ID=sa; Password=pass"
> Doesn't work
> "Data Source=PETER-DEVELOPER\va3,1433;Initial Catalog=VA2005;Integrated
> Security=SSPI;User ID=sa; Password=pass"
> Doesn't work
> "Data Source=Peter-developer\VA3,1433;Network
> Library=DBMSSOCN;Integrated Security=SSPI;Initial Catalog=VA2005;User
> ID=peter;Password=peter"
> Doesn't work ether
> You say something about making a new user, I don't understand that,
> could you explain it again please
>
sql
Monday, March 19, 2012
Can multiple workstations running SQL 2005 Server Express attach to the same database files on a
Can multiple instances of SQL 2005 Express attach to the same database files on a network share? I have seen this done before with MSDE where the database files are stored on the server, but instead of having a SQL server running on the network and then connecting to it, only the database files exist on the network share and the users connect through MSDE running on the local machine. Is this possible with SQL2005Express? I do not have the ability to share an SQL instance from one workstation to another nor do I have the ability to install an instance on the corporate server. Is it as simple as creating the database and storing the files on the share then attaching the database to the SQL Instance on each workstation?
No and No. You can only attach a database file to a single instance at a time and SQL Express does not support attaching files from a remote source, only local drives.
Mike
|||As Michael indicated, that is not possible -and it is not possible with MSDE either.
You will have to install a SQL Server Express somewhere, and that will also be the location for the data files. I suggest that you communicate and negotiate with your network admins, and of course, get the 'clients' involved too.
Otherwise, you will be limited to using an Access *.mdb file -which can be stored on a file server.
Can MSDE work as SQL Server?
I plan on replacing a SQL2000 database with MSDE for lowering budget.
Can we script up the SQL database (with SPs, triggers, and UDFs) and recreate it in MSDE?
Thanks.All SQL Server code will work fine on MSDE. The restriction is that it is restricted to 8 concurrent operations. At that point, there is a governer that kiks in to slow down operations.
Can we script up the SQL database (with SPs, triggers, and UDFs) and recreate it in MSDE?
Thanks.All SQL Server code will work fine on MSDE. The restriction is that it is restricted to 8 concurrent operations. At that point, there is a governer that kiks in to slow down operations.
http://msdn.microsoft.com/library/?url=/library/en-us/architec/8_ar_sa2_0ciq.asp?frame=true
http://www.microsoft.com/sql/msde/|||How can we create/maintain tables, views, stored procedures, triggers and UDFs in MSDE?
Thanks|||through SQL code. CREATE TABLE, CREATE VIEW, ALTER PRCEDURE etc... see Books Online
(you can also connect with the SQL Server client tools, and other SQL Server management tools can be found on the web)
Can MSDE trigger call a .NET remote object?
Hi,
I wonder if MSDE trigger can call a remote .NET object
,i want to get notify when a new row was added or changed
also if I have an access application(forms etc...) can I still use it with
MSDE?
thanks in advance.
hi Julia,
"Julia" <codewizard@.012.net.il> ha scritto nel messaggio
news:u6ih4$XwEHA.4048@.TK2MSFTNGP15.phx.gbl
> Hi,
> I wonder if MSDE trigger can call a remote .NET object
> ,i want to get notify when a new row was added or changed
>
actually it should not be the case... you could perhaps "shell" out to
server's local resources, but this is not a good practice :D
this is usually not the correct scenario for client server applications...
if you really need something like that, schedule a data refresh from time to
time, say, every hour :D
stop kidding, ok.. perhaps you should rely on other forms of data
investigation..
> also if I have an access application(forms etc...) can I still use it
> with MSDE?
>
usually yes... an .ADP project will manage you connection(s) to a SQL
Server/MSDE database, while the Access project only includes forms
definitions, reports and so on..
http://www.amazon.com/exec/obidos/tg...glance&s=books
... a little dated, but still valuable book by Mary Chipman
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I wonder if MSDE trigger can call a remote .NET object
,i want to get notify when a new row was added or changed
also if I have an access application(forms etc...) can I still use it with
MSDE?
thanks in advance.
hi Julia,
"Julia" <codewizard@.012.net.il> ha scritto nel messaggio
news:u6ih4$XwEHA.4048@.TK2MSFTNGP15.phx.gbl
> Hi,
> I wonder if MSDE trigger can call a remote .NET object
> ,i want to get notify when a new row was added or changed
>
actually it should not be the case... you could perhaps "shell" out to
server's local resources, but this is not a good practice :D
this is usually not the correct scenario for client server applications...
if you really need something like that, schedule a data refresh from time to
time, say, every hour :D
stop kidding, ok.. perhaps you should rely on other forms of data
investigation..
> also if I have an access application(forms etc...) can I still use it
> with MSDE?
>
usually yes... an .ADP project will manage you connection(s) to a SQL
Server/MSDE database, while the Access project only includes forms
definitions, reports and so on..
http://www.amazon.com/exec/obidos/tg...glance&s=books
... a little dated, but still valuable book by Mary Chipman
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Can MSDE or SQL Server send an active message to the client?
when a new record is inserted into one of the table?
Or, we should maintain the messaging by ourselves?
Thanks.
hi,
zhaounknown wrote:
> when a new record is inserted into one of the table?
> Or, we should maintain the messaging by ourselves?
> Thanks.
actually this is a very bad practice as you'd overhelm the server
activities..
what kind of message would you like to send? over the whole network?
you can perhaps implement some NET SEND in insert/update/delete trigger, but
again, this is very poor..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||In addition to what Andrea mentioned, take a look at the SqlDependency class
in VS.NET2005/SQL Server 2005. You can use that with SQL Express (the MSDE
replacement). I suspect it's just what you're looking for.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3b036cF6fh560U1@.individual.net...
> hi,
> zhaounknown wrote:
> actually this is a very bad practice as you'd overhelm the server
> activities..
> what kind of message would you like to send? over the whole network?
> you can perhaps implement some NET SEND in insert/update/delete trigger,
> but
> again, this is very poor..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Or, we should maintain the messaging by ourselves?
Thanks.
hi,
zhaounknown wrote:
> when a new record is inserted into one of the table?
> Or, we should maintain the messaging by ourselves?
> Thanks.
actually this is a very bad practice as you'd overhelm the server
activities..
what kind of message would you like to send? over the whole network?
you can perhaps implement some NET SEND in insert/update/delete trigger, but
again, this is very poor..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||In addition to what Andrea mentioned, take a look at the SqlDependency class
in VS.NET2005/SQL Server 2005. You can use that with SQL Express (the MSDE
replacement). I suspect it's just what you're looking for.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3b036cF6fh560U1@.individual.net...
> hi,
> zhaounknown wrote:
> actually this is a very bad practice as you'd overhelm the server
> activities..
> what kind of message would you like to send? over the whole network?
> you can perhaps implement some NET SEND in insert/update/delete trigger,
> but
> again, this is very poor..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Can Msde import DBF files in my tables
Hi Sergio,
This took me a while to figure out, but it is really simple. From my
message a few weeks ago...
"Just to update people (and for my future reference when I search Google
for my name), using DTS makes it VERY simple to import DBF files into SQL.
What screwed me up was two things:
1) While it may be possible to do in MSDE, it is very simple using DTS
on the server. I logged into my client's SQL server and ran DTS, filled
out a few options and imported all the FoxPro info into a new SQL database.
2) DTS is actually found via: Start Program > Microsoft SQL Server >
Import Export Data ... this launches the DTS wizard. I was looking
specifically for something called DTS. I should have tried the
import/export option first"
Hope this helps
Richard
Sergio wrote:
> Hi, y really now if its possible in MSDE,
> can i import DBF files in my tables of MSDE?, how?, i need import in Tsql,
> how?
> thanks
Yes, it's easy in DTS but you can also save a DTS package that can then be
run in the MSDE.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Richard Fagen" <no_spam@.my_isp.com> wrote in message
news:uX2K49CHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Hi Sergio,
> This took me a while to figure out, but it is really simple. From my
> message a few weeks ago...
> "Just to update people (and for my future reference when I search Google
> for my name), using DTS makes it VERY simple to import DBF files into SQL.
> What screwed me up was two things:
> 1) While it may be possible to do in MSDE, it is very simple using DTS
> on the server. I logged into my client's SQL server and ran DTS, filled
> out a few options and imported all the FoxPro info into a new SQL
database.
> 2) DTS is actually found via: Start Program > Microsoft SQL Server >
> Import Export Data ... this launches the DTS wizard. I was looking
> specifically for something called DTS. I should have tried the
> import/export option first"
>
> Hope this helps
> Richard
> Sergio wrote:
Tsql,
This took me a while to figure out, but it is really simple. From my
message a few weeks ago...
"Just to update people (and for my future reference when I search Google
for my name), using DTS makes it VERY simple to import DBF files into SQL.
What screwed me up was two things:
1) While it may be possible to do in MSDE, it is very simple using DTS
on the server. I logged into my client's SQL server and ran DTS, filled
out a few options and imported all the FoxPro info into a new SQL database.
2) DTS is actually found via: Start Program > Microsoft SQL Server >
Import Export Data ... this launches the DTS wizard. I was looking
specifically for something called DTS. I should have tried the
import/export option first"
Hope this helps
Richard
Sergio wrote:
> Hi, y really now if its possible in MSDE,
> can i import DBF files in my tables of MSDE?, how?, i need import in Tsql,
> how?
> thanks
Yes, it's easy in DTS but you can also save a DTS package that can then be
run in the MSDE.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Richard Fagen" <no_spam@.my_isp.com> wrote in message
news:uX2K49CHEHA.2744@.TK2MSFTNGP10.phx.gbl...
> Hi Sergio,
> This took me a while to figure out, but it is really simple. From my
> message a few weeks ago...
> "Just to update people (and for my future reference when I search Google
> for my name), using DTS makes it VERY simple to import DBF files into SQL.
> What screwed me up was two things:
> 1) While it may be possible to do in MSDE, it is very simple using DTS
> on the server. I logged into my client's SQL server and ran DTS, filled
> out a few options and imported all the FoxPro info into a new SQL
database.
> 2) DTS is actually found via: Start Program > Microsoft SQL Server >
> Import Export Data ... this launches the DTS wizard. I was looking
> specifically for something called DTS. I should have tried the
> import/export option first"
>
> Hope this helps
> Richard
> Sergio wrote:
Tsql,
Can MSDE Do Log Shipping?
The subject line pretty much says it all. I'be been trying to use the SQL
Enterprise Administrator that came with SQL 2000 Enterprise to configure log
shipping, but the checkbox does not appear for databases on my MSDE servers,
only for the databases on my SQL 2000 Standard servers. Is there a way to set
up log shipping with MSDE?
--EricYes and no.
Log shipping is built in to Enterprise Edition only. However, there is
nothing preventing you from writing your own or using a third-party Log
Shipping solution with MSDE. The SQL 2000 Resource Kit even has an example.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Eric Robinson" <eric@._nospam_nvipa.com> wrote in message
news:CFN379450764603357@.news.microsoft.com...
> The subject line pretty much says it all. I'be been trying to use the SQL
> Enterprise Administrator that came with SQL 2000 Enterprise to configure
log
> shipping, but the checkbox does not appear for databases on my MSDE
servers,
> only for the databases on my SQL 2000 Standard servers. Is there a way to
set
> up log shipping with MSDE?
> --Eric|||To expand on Geoff's post, here is a site that you may find helpful:
http://sqlguy.home.comcast.net/logship.htm
-- Keith
"Eric Robinson" <eric@._nospam_nvipa.com> wrote in message =news:CFN379450764603357@.news.microsoft.com...
> The subject line pretty much says it all. I'be been trying to use the =SQL > Enterprise Administrator that came with SQL 2000 Enterprise to =configure log > shipping, but the checkbox does not appear for databases on my MSDE =servers, > only for the databases on my SQL 2000 Standard servers. Is there a way =to set > up log shipping with MSDE?
> > --Eric
Enterprise Administrator that came with SQL 2000 Enterprise to configure log
shipping, but the checkbox does not appear for databases on my MSDE servers,
only for the databases on my SQL 2000 Standard servers. Is there a way to set
up log shipping with MSDE?
--EricYes and no.
Log shipping is built in to Enterprise Edition only. However, there is
nothing preventing you from writing your own or using a third-party Log
Shipping solution with MSDE. The SQL 2000 Resource Kit even has an example.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Eric Robinson" <eric@._nospam_nvipa.com> wrote in message
news:CFN379450764603357@.news.microsoft.com...
> The subject line pretty much says it all. I'be been trying to use the SQL
> Enterprise Administrator that came with SQL 2000 Enterprise to configure
log
> shipping, but the checkbox does not appear for databases on my MSDE
servers,
> only for the databases on my SQL 2000 Standard servers. Is there a way to
set
> up log shipping with MSDE?
> --Eric|||To expand on Geoff's post, here is a site that you may find helpful:
http://sqlguy.home.comcast.net/logship.htm
-- Keith
"Eric Robinson" <eric@._nospam_nvipa.com> wrote in message =news:CFN379450764603357@.news.microsoft.com...
> The subject line pretty much says it all. I'be been trying to use the =SQL > Enterprise Administrator that came with SQL 2000 Enterprise to =configure log > shipping, but the checkbox does not appear for databases on my MSDE =servers, > only for the databases on my SQL 2000 Standard servers. Is there a way =to set > up log shipping with MSDE?
> > --Eric
Can MSDE and SQL live on the same system?
Hey everyone,
We are running MSDE on a Windows 200 server and it has data in it. What I
would like to know is can we also install MSSQL 2005 on that server and have
assess to both databases. Is there anything we have to do to install it and
make sure it doesn't overwrite or delete the MSDE database?
TIA,
Claytonhi Clayton,
Clayton Sutton wrote:
> Hey everyone,
> We are running MSDE on a Windows 200 server and it has data in it. What I
> would like to know is can we also install MSSQL 2005 on that
> server and have assess to both databases. Is there anything we have
> to do to install it and make sure it doesn't overwrite or delete the
> MSDE database?
MSDE and SQL Server 2005 can coexist on the same computer... just pay
attention, at installation time, not to "upgrade" the MSDE instance to a SQL
Server 2005 one..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Yes this is possible, you just have to install it as a default or named
instance, which doesn=B4t equal the instance name of the MSDE, although
I doubt that this is possible through the installer to crash the system
that way. They are using different ports, so co-existence on the system
is possible.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Just interesting, why you do not want a run both databases on sql 2005?
Andris
Clayton Sutton wrote:
> Hey everyone,
> We are running MSDE on a Windows 200 server and it has data in it. What I
> would like to know is can we also install MSSQL 2005 on that server and ha
ve
> assess to both databases. Is there anything we have to do to install it a
nd
> make sure it doesn't overwrite or delete the MSDE database?
>
> TIA,
> Clayton
>|||An old app. that one dept. has been using for years was running on MSDE.
Now they are moving to a new program that uses MSSQL 2000/2005. However,
the old data is going to stay in the MSDE database (unless that dept. wants
to pay someone to do a data export/import into MSSQL). I just wanted to
make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE
and all of the old data therein.
Clayton
"Andris" <spameris@.gmail.com> wrote in message
news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Just interesting, why you do not want a run both databases on sql 2005?
> Andris
> Clayton Sutton wrote:|||I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches.
Simple backup/restore. With MSDE i think u can too, backup that db and
restore to MSSQL 2005. How i understand MSDE is some as MSSQL with some
restrictions on db size,replications etc. All who run un MSDE must run
un MSSQL. I have few msde servers who replicating with MSSQL, sometimes
i need open archive of these msde databases, i do this on MSSQL without
problems.
Sry my poor english
Andris
Clayton Sutton wrote:
> An old app. that one dept. has been using for years was running on MSDE.
> Now they are moving to a new program that uses MSSQL 2000/2005. However,
> the old data is going to stay in the MSDE database (unless that dept. want
s
> to pay someone to do a data export/import into MSSQL). I just wanted to
> make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE
> and all of the old data therein.
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>
>
>|||Hey Andris,
First thing, your english is fine. Don't ever apologize for that. Truth be
told, I can't spell.
Backing up MSDE is a little tricky. Most backup software doesn't have a
connector for MSDE so backing up and restore becomes a little harder.
The command line command to back one up is:
C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk =
'c:\mssql7\backup\dbname.bak'"
It took me forever to find that command, and I don't know what the command
is to restore it.
Clayton
"Andris" <spameris@.gmail.com> wrote in message
news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches. Simple
>backup/restore. With MSDE i think u can too, backup that db and restore to
>MSSQL 2005. How i understand MSDE is some as MSSQL with some restrictions
>on db size,replications etc. All who run un MSDE must run un MSSQL. I have
>few msde servers who replicating with MSSQL, sometimes i need open archive
>of these msde databases, i do this on MSSQL without problems.
> Sry my poor english
> Andris
> Clayton Sutton wrote:|||For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server 2000
(the MSDE info), you can download a copy of Books Online (BOL) at
http://www.microsoft.com/downloads/...DisplayLang=en.
Using the example syntax you provided, it would probably be something like:
osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM
DISK='c:\mssql7\backup\dbname.bak'"
Note, however, that I haven't tested that. :-)
Sincerely,
Steve Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clayton Sutton" <none@.none.com> wrote in message
news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
> Hey Andris,
> First thing, your english is fine. Don't ever apologize for that. Truth
> be told, I can't spell.
> Backing up MSDE is a little tricky. Most backup software doesn't have a
> connector for MSDE so backing up and restore becomes a little harder.
> The command line command to back one up is:
> C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk =
> 'c:\mssql7\backup\dbname.bak'"
> It took me forever to find that command, and I don't know what the command
> is to restore it.
>
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>|||Hey Steve,
Would that restore the DB to MSDE only. What if you wanted to restore it
into MSSQL 2000 or 2005? That's really what we are talking about, how to
move from MSDE to MSSQL 2000/2005. Get the data out of MSDE and into MSSQL.
Clayton
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in messa
ge
news:uIP9O6QdGHA.1436@.TK2MSFTNGP05.phx.gbl...
> For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
> http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server
> 2000 (the MSDE info), you can download a copy of Books Online (BOL) at
> http://www.microsoft.com/downloads/...DisplayLang=en.
> Using the example syntax you provided, it would probably be something
> like:
> osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM
> DISK='c:\mssql7\backup\dbname.bak'"
> Note, however, that I haven't tested that. :-)
> --
> Sincerely,
> Steve Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clayton Sutton" <none@.none.com> wrote in message
> news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
>|||MSDE is SQL Server. So you can both attach and restore an MSDE 2000 database
into SQL Server 2000 or
2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Clayton" <none@.none.com> wrote in message news:8GV8g.100380$JV1.10779@.fe05.news.easynews.co
m...
> Hey Steve,
> Would that restore the DB to MSDE only. What if you wanted to restore it
into MSSQL 2000 or 2005?
> That's really what we are talking about, how to move from MSDE to MSSQL 20
00/2005. Get the data
> out of MSDE and into MSSQL.
>
> Clayton
>
> "Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in mes
sage
> news:uIP9O6QdGHA.1436@.TK2MSFTNGP05.phx.gbl...
>
We are running MSDE on a Windows 200 server and it has data in it. What I
would like to know is can we also install MSSQL 2005 on that server and have
assess to both databases. Is there anything we have to do to install it and
make sure it doesn't overwrite or delete the MSDE database?
TIA,
Claytonhi Clayton,
Clayton Sutton wrote:
> Hey everyone,
> We are running MSDE on a Windows 200 server and it has data in it. What I
> would like to know is can we also install MSSQL 2005 on that
> server and have assess to both databases. Is there anything we have
> to do to install it and make sure it doesn't overwrite or delete the
> MSDE database?
MSDE and SQL Server 2005 can coexist on the same computer... just pay
attention, at installation time, not to "upgrade" the MSDE instance to a SQL
Server 2005 one..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Yes this is possible, you just have to install it as a default or named
instance, which doesn=B4t equal the instance name of the MSDE, although
I doubt that this is possible through the installer to crash the system
that way. They are using different ports, so co-existence on the system
is possible.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--|||Just interesting, why you do not want a run both databases on sql 2005?
Andris
Clayton Sutton wrote:
> Hey everyone,
> We are running MSDE on a Windows 200 server and it has data in it. What I
> would like to know is can we also install MSSQL 2005 on that server and ha
ve
> assess to both databases. Is there anything we have to do to install it a
nd
> make sure it doesn't overwrite or delete the MSDE database?
>
> TIA,
> Clayton
>|||An old app. that one dept. has been using for years was running on MSDE.
Now they are moving to a new program that uses MSSQL 2000/2005. However,
the old data is going to stay in the MSDE database (unless that dept. wants
to pay someone to do a data export/import into MSSQL). I just wanted to
make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE
and all of the old data therein.
Clayton
"Andris" <spameris@.gmail.com> wrote in message
news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Just interesting, why you do not want a run both databases on sql 2005?
> Andris
> Clayton Sutton wrote:|||I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches.
Simple backup/restore. With MSDE i think u can too, backup that db and
restore to MSSQL 2005. How i understand MSDE is some as MSSQL with some
restrictions on db size,replications etc. All who run un MSDE must run
un MSSQL. I have few msde servers who replicating with MSSQL, sometimes
i need open archive of these msde databases, i do this on MSSQL without
problems.
Sry my poor english
Andris
Clayton Sutton wrote:
> An old app. that one dept. has been using for years was running on MSDE.
> Now they are moving to a new program that uses MSSQL 2000/2005. However,
> the old data is going to stay in the MSDE database (unless that dept. want
s
> to pay someone to do a data export/import into MSSQL). I just wanted to
> make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE
> and all of the old data therein.
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>
>
>|||Hey Andris,
First thing, your english is fine. Don't ever apologize for that. Truth be
told, I can't spell
.Backing up MSDE is a little tricky. Most backup software doesn't have a
connector for MSDE so backing up and restore becomes a little harder.
The command line command to back one up is:
C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk =
'c:\mssql7\backup\dbname.bak'"
It took me forever to find that command, and I don't know what the command
is to restore it.
Clayton
"Andris" <spameris@.gmail.com> wrote in message
news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches. Simple
>backup/restore. With MSDE i think u can too, backup that db and restore to
>MSSQL 2005. How i understand MSDE is some as MSSQL with some restrictions
>on db size,replications etc. All who run un MSDE must run un MSSQL. I have
>few msde servers who replicating with MSSQL, sometimes i need open archive
>of these msde databases, i do this on MSSQL without problems.
> Sry my poor english
> Andris
> Clayton Sutton wrote:|||For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server 2000
(the MSDE info), you can download a copy of Books Online (BOL) at
http://www.microsoft.com/downloads/...DisplayLang=en.
Using the example syntax you provided, it would probably be something like:
osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM
DISK='c:\mssql7\backup\dbname.bak'"
Note, however, that I haven't tested that. :-)
Sincerely,
Steve Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clayton Sutton" <none@.none.com> wrote in message
news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
> Hey Andris,
> First thing, your english is fine. Don't ever apologize for that. Truth
> be told, I can't spell
.> Backing up MSDE is a little tricky. Most backup software doesn't have a
> connector for MSDE so backing up and restore becomes a little harder.
> The command line command to back one up is:
> C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk =
> 'c:\mssql7\backup\dbname.bak'"
> It took me forever to find that command, and I don't know what the command
> is to restore it.
>
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>|||Hey Steve,
Would that restore the DB to MSDE only. What if you wanted to restore it
into MSSQL 2000 or 2005? That's really what we are talking about, how to
move from MSDE to MSSQL 2000/2005. Get the data out of MSDE and into MSSQL.
Clayton
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in messa
ge
news:uIP9O6QdGHA.1436@.TK2MSFTNGP05.phx.gbl...
> For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
> http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server
> 2000 (the MSDE info), you can download a copy of Books Online (BOL) at
> http://www.microsoft.com/downloads/...DisplayLang=en.
> Using the example syntax you provided, it would probably be something
> like:
> osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM
> DISK='c:\mssql7\backup\dbname.bak'"
> Note, however, that I haven't tested that. :-)
> --
> Sincerely,
> Steve Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clayton Sutton" <none@.none.com> wrote in message
> news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
>|||MSDE is SQL Server. So you can both attach and restore an MSDE 2000 database
into SQL Server 2000 or
2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Clayton" <none@.none.com> wrote in message news:8GV8g.100380$JV1.10779@.fe05.news.easynews.co
m...
> Hey Steve,
> Would that restore the DB to MSDE only. What if you wanted to restore it
into MSSQL 2000 or 2005?
> That's really what we are talking about, how to move from MSDE to MSSQL 20
00/2005. Get the data
> out of MSDE and into MSSQL.
>
> Clayton
>
> "Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in mes
sage
> news:uIP9O6QdGHA.1436@.TK2MSFTNGP05.phx.gbl...
>
Can MSDE and SQL live on the same system?
Hey everyone,
We are running MSDE on a Windows 200 server and it has data in it. What I
would like to know is can we also install MSSQL 2005 on that server and have
assess to both databases. Is there anything we have to do to install it and
make sure it doesn't overwrite or delete the MSDE database?
TIA,
Claytonhi Clayton,
Clayton Sutton wrote:
> Hey everyone,
> We are running MSDE on a Windows 200 server and it has data in it. What I
> would like to know is can we also install MSSQL 2005 on that
> server and have assess to both databases. Is there anything we have
> to do to install it and make sure it doesn't overwrite or delete the
> MSDE database?
MSDE and SQL Server 2005 can coexist on the same computer... just pay
attention, at installation time, not to "upgrade" the MSDE instance to a SQL
Server 2005 one..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Yes this is possible, you just have to install it as a default or named
instance, which doesn=B4t equal the instance name of the MSDE, although
I doubt that this is possible through the installer to crash the system
that way. They are using different ports, so co-existence on the system
is possible.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Just interesting, why you do not want a run both databases on sql 2005?
Andris
Clayton Sutton wrote:
> Hey everyone,
> We are running MSDE on a Windows 200 server and it has data in it. What I
> would like to know is can we also install MSSQL 2005 on that server and have
> assess to both databases. Is there anything we have to do to install it and
> make sure it doesn't overwrite or delete the MSDE database?
>
> TIA,
> Clayton
>|||An old app. that one dept. has been using for years was running on MSDE.
Now they are moving to a new program that uses MSSQL 2000/2005. However,
the old data is going to stay in the MSDE database (unless that dept. wants
to pay someone to do a data export/import into MSSQL). I just wanted to
make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE
and all of the old data therein.
Clayton
"Andris" <spameris@.gmail.com> wrote in message
news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
> Just interesting, why you do not want a run both databases on sql 2005?
> Andris
> Clayton Sutton wrote:
>> Hey everyone,
>> We are running MSDE on a Windows 200 server and it has data in it. What
>> I would like to know is can we also install MSSQL 2005 on that server and
>> have assess to both databases. Is there anything we have to do to
>> install it and make sure it doesn't overwrite or delete the MSDE
>> database?
>>
>> TIA,
>> Clayton|||I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches.
Simple backup/restore. With MSDE i think u can too, backup that db and
restore to MSSQL 2005. How i understand MSDE is some as MSSQL with some
restrictions on db size,replications etc. All who run un MSDE must run
un MSSQL. I have few msde servers who replicating with MSSQL, sometimes
i need open archive of these msde databases, i do this on MSSQL without
problems.
Sry my poor english
Andris
Clayton Sutton wrote:
> An old app. that one dept. has been using for years was running on MSDE.
> Now they are moving to a new program that uses MSSQL 2000/2005. However,
> the old data is going to stay in the MSDE database (unless that dept. wants
> to pay someone to do a data export/import into MSSQL). I just wanted to
> make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE
> and all of the old data therein.
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>Hey everyone,
>>We are running MSDE on a Windows 200 server and it has data in it. What
>>I would like to know is can we also install MSSQL 2005 on that server and
>>have assess to both databases. Is there anything we have to do to
>>install it and make sure it doesn't overwrite or delete the MSDE
>>database?
>>
>>TIA,
>>Clayton
>
>|||Hey Andris,
First thing, your english is fine. Don't ever apologize for that. Truth be
told, I can't spell :).
Backing up MSDE is a little tricky. Most backup software doesn't have a
connector for MSDE so backing up and restore becomes a little harder.
The command line command to back one up is:
C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk ='c:\mssql7\backup\dbname.bak'"
It took me forever to find that command, and I don't know what the command
is to restore it.
Clayton
"Andris" <spameris@.gmail.com> wrote in message
news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches. Simple
>backup/restore. With MSDE i think u can too, backup that db and restore to
>MSSQL 2005. How i understand MSDE is some as MSSQL with some restrictions
>on db size,replications etc. All who run un MSDE must run un MSSQL. I have
>few msde servers who replicating with MSSQL, sometimes i need open archive
>of these msde databases, i do this on MSSQL without problems.
> Sry my poor english
> Andris
> Clayton Sutton wrote:
>> An old app. that one dept. has been using for years was running on MSDE.
>> Now they are moving to a new program that uses MSSQL 2000/2005. However,
>> the old data is going to stay in the MSDE database (unless that dept.
>> wants to pay someone to do a data export/import into MSSQL). I just
>> wanted to make sure installing MSSQL on the same system as MSDE didn't
>> wipe out MSDE and all of the old data therein.
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message
>> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>Hey everyone,
>>We are running MSDE on a Windows 200 server and it has data in it. What
>>I would like to know is can we also install MSSQL 2005 on that server
>>and have assess to both databases. Is there anything we have to do to
>>install it and make sure it doesn't overwrite or delete the MSDE
>>database?
>>
>>TIA,
>>Clayton
>>|||For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server 2000
(the MSDE info), you can download a copy of Books Online (BOL) at
http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en.
Using the example syntax you provided, it would probably be something like:
osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM
DISK='c:\mssql7\backup\dbname.bak'"
Note, however, that I haven't tested that. :-)
--
Sincerely,
Steve Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clayton Sutton" <none@.none.com> wrote in message
news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
> Hey Andris,
> First thing, your english is fine. Don't ever apologize for that. Truth
> be told, I can't spell :).
> Backing up MSDE is a little tricky. Most backup software doesn't have a
> connector for MSDE so backing up and restore becomes a little harder.
> The command line command to back one up is:
> C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk => 'c:\mssql7\backup\dbname.bak'"
> It took me forever to find that command, and I don't know what the command
> is to restore it.
>
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches. Simple
>>backup/restore. With MSDE i think u can too, backup that db and restore to
>>MSSQL 2005. How i understand MSDE is some as MSSQL with some restrictions
>>on db size,replications etc. All who run un MSDE must run un MSSQL. I have
>>few msde servers who replicating with MSSQL, sometimes i need open archive
>>of these msde databases, i do this on MSSQL without problems.
>> Sry my poor english
>> Andris
>> Clayton Sutton wrote:
>> An old app. that one dept. has been using for years was running on MSDE.
>> Now they are moving to a new program that uses MSSQL 2000/2005.
>> However, the old data is going to stay in the MSDE database (unless that
>> dept. wants to pay someone to do a data export/import into MSSQL). I
>> just wanted to make sure installing MSSQL on the same system as MSDE
>> didn't wipe out MSDE and all of the old data therein.
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message
>> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>Hey everyone,
>>We are running MSDE on a Windows 200 server and it has data in it.
>>What I would like to know is can we also install MSSQL 2005 on that
>>server and have assess to both databases. Is there anything we have to
>>do to install it and make sure it doesn't overwrite or delete the MSDE
>>database?
>>
>>TIA,
>>Clayton
>>
>|||Hey Steve,
Would that restore the DB to MSDE only. What if you wanted to restore it
into MSSQL 2000 or 2005? That's really what we are talking about, how to
move from MSDE to MSSQL 2000/2005. Get the data out of MSDE and into MSSQL.
Clayton
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in message
news:uIP9O6QdGHA.1436@.TK2MSFTNGP05.phx.gbl...
> For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
> http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server
> 2000 (the MSDE info), you can download a copy of Books Online (BOL) at
> http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en.
> Using the example syntax you provided, it would probably be something
> like:
> osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM
> DISK='c:\mssql7\backup\dbname.bak'"
> Note, however, that I haven't tested that. :-)
> --
> Sincerely,
> Steve Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clayton Sutton" <none@.none.com> wrote in message
> news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
>> Hey Andris,
>> First thing, your english is fine. Don't ever apologize for that. Truth
>> be told, I can't spell :).
>> Backing up MSDE is a little tricky. Most backup software doesn't have a
>> connector for MSDE so backing up and restore becomes a little harder.
>> The command line command to back one up is:
>> C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk =>> 'c:\mssql7\backup\dbname.bak'"
>> It took me forever to find that command, and I don't know what the
>> command is to restore it.
>>
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message
>> news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches.
>>Simple backup/restore. With MSDE i think u can too, backup that db and
>>restore to MSSQL 2005. How i understand MSDE is some as MSSQL with some
>>restrictions on db size,replications etc. All who run un MSDE must run un
>>MSSQL. I have few msde servers who replicating with MSSQL, sometimes i
>>need open archive of these msde databases, i do this on MSSQL without
>>problems.
>> Sry my poor english
>> Andris
>> Clayton Sutton wrote:
>> An old app. that one dept. has been using for years was running on
>> MSDE. Now they are moving to a new program that uses MSSQL 2000/2005.
>> However, the old data is going to stay in the MSDE database (unless
>> that dept. wants to pay someone to do a data export/import into MSSQL).
>> I just wanted to make sure installing MSSQL on the same system as MSDE
>> didn't wipe out MSDE and all of the old data therein.
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message
>> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>Hey everyone,
>>We are running MSDE on a Windows 200 server and it has data in it.
>>What I would like to know is can we also install MSSQL 2005 on that
>>server and have assess to both databases. Is there anything we have
>>to do to install it and make sure it doesn't overwrite or delete the
>>MSDE database?
>>
>>TIA,
>>Clayton
>>
>|||MSDE is SQL Server. So you can both attach and restore an MSDE 2000 database into SQL Server 2000 or
2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Clayton" <none@.none.com> wrote in message news:8GV8g.100380$JV1.10779@.fe05.news.easynews.com...
> Hey Steve,
> Would that restore the DB to MSDE only. What if you wanted to restore it into MSSQL 2000 or 2005?
> That's really what we are talking about, how to move from MSDE to MSSQL 2000/2005. Get the data
> out of MSDE and into MSSQL.
>
> Clayton
>
> "Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in message
> news:uIP9O6QdGHA.1436@.TK2MSFTNGP05.phx.gbl...
>> For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
>> http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server 2000 (the MSDE info), you
>> can download a copy of Books Online (BOL) at
>> http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en.
>> Using the example syntax you provided, it would probably be something like:
>> osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM DISK='c:\mssql7\backup\dbname.bak'"
>> Note, however, that I haven't tested that. :-)
>> --
>> Sincerely,
>> Steve Dybing
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> "Clayton Sutton" <none@.none.com> wrote in message
>> news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
>> Hey Andris,
>> First thing, your english is fine. Don't ever apologize for that. Truth be told, I can't spell
>> :).
>> Backing up MSDE is a little tricky. Most backup software doesn't have a connector for MSDE so
>> backing up and restore becomes a little harder.
>> The command line command to back one up is:
>> C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk =>> 'c:\mssql7\backup\dbname.bak'"
>> It took me forever to find that command, and I don't know what the command is to restore it.
>>
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches. Simple backup/restore. With
>>MSDE i think u can too, backup that db and restore to MSSQL 2005. How i understand MSDE is some
>>as MSSQL with some restrictions on db size,replications etc. All who run un MSDE must run un
>>MSSQL. I have few msde servers who replicating with MSSQL, sometimes i need open archive of
>>these msde databases, i do this on MSSQL without problems.
>> Sry my poor english
>> Andris
>> Clayton Sutton wrote:
>> An old app. that one dept. has been using for years was running on MSDE. Now they are moving
>> to a new program that uses MSSQL 2000/2005. However, the old data is going to stay in the MSDE
>> database (unless that dept. wants to pay someone to do a data export/import into MSSQL). I
>> just wanted to make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE and
>> all of the old data therein.
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>>Hey everyone,
>>>
>>>We are running MSDE on a Windows 200 server and it has data in it. What I would like to know
>>>is can we also install MSSQL 2005 on that server and have assess to both databases. Is there
>>>anything we have to do to install it and make sure it doesn't overwrite or delete the MSDE
>>>database?
>>>
>>>
>>>TIA,
>>>
>>>Clayton
>>
>>
>|||From your post it sounds like you believe that MSSQL and MSDE are two
different database formats. They are not. MSDE is merely a scaled-down
version of SQL Server, and the file formats are identical.
I, personally, develop in MSDE on my development machine, and then I make
changes to the live database which is running on SQL Server. When I need a
new copy of the data, I download a backup file from the SQL Server database
and run it in my MSDE. The two formats are identical.
Thus, while installing MSSQL might create conflicts with running MSDE, the
*data itself* will remain untouched. Since your MSDE data is in SQL 7
format, there may be issues with running your data on a later version of
MSSQL, but those should be able to be resolved.
"Clayton Sutton" <none@.none.com> wrote in message
news:xIt8g.391355$4P2.48017@.fe03.news.easynews.com...
> An old app. that one dept. has been using for years was running on MSDE.
> Now they are moving to a new program that uses MSSQL 2000/2005. However,
> the old data is going to stay in the MSDE database (unless that dept.
> wants to pay someone to do a data export/import into MSSQL). I just
> wanted to make sure installing MSSQL on the same system as MSDE didn't
> wipe out MSDE and all of the old data therein.
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>> Just interesting, why you do not want a run both databases on sql 2005?
>> Andris
>> Clayton Sutton wrote:
>> Hey everyone,
>> We are running MSDE on a Windows 200 server and it has data in it. What
>> I would like to know is can we also install MSSQL 2005 on that server
>> and have assess to both databases. Is there anything we have to do to
>> install it and make sure it doesn't overwrite or delete the MSDE
>> database?
>>
>> TIA,
>> Clayton
>
We are running MSDE on a Windows 200 server and it has data in it. What I
would like to know is can we also install MSSQL 2005 on that server and have
assess to both databases. Is there anything we have to do to install it and
make sure it doesn't overwrite or delete the MSDE database?
TIA,
Claytonhi Clayton,
Clayton Sutton wrote:
> Hey everyone,
> We are running MSDE on a Windows 200 server and it has data in it. What I
> would like to know is can we also install MSSQL 2005 on that
> server and have assess to both databases. Is there anything we have
> to do to install it and make sure it doesn't overwrite or delete the
> MSDE database?
MSDE and SQL Server 2005 can coexist on the same computer... just pay
attention, at installation time, not to "upgrade" the MSDE instance to a SQL
Server 2005 one..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Yes this is possible, you just have to install it as a default or named
instance, which doesn=B4t equal the instance name of the MSDE, although
I doubt that this is possible through the installer to crash the system
that way. They are using different ports, so co-existence on the system
is possible.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--|||Just interesting, why you do not want a run both databases on sql 2005?
Andris
Clayton Sutton wrote:
> Hey everyone,
> We are running MSDE on a Windows 200 server and it has data in it. What I
> would like to know is can we also install MSSQL 2005 on that server and have
> assess to both databases. Is there anything we have to do to install it and
> make sure it doesn't overwrite or delete the MSDE database?
>
> TIA,
> Clayton
>|||An old app. that one dept. has been using for years was running on MSDE.
Now they are moving to a new program that uses MSSQL 2000/2005. However,
the old data is going to stay in the MSDE database (unless that dept. wants
to pay someone to do a data export/import into MSSQL). I just wanted to
make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE
and all of the old data therein.
Clayton
"Andris" <spameris@.gmail.com> wrote in message
news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
> Just interesting, why you do not want a run both databases on sql 2005?
> Andris
> Clayton Sutton wrote:
>> Hey everyone,
>> We are running MSDE on a Windows 200 server and it has data in it. What
>> I would like to know is can we also install MSSQL 2005 on that server and
>> have assess to both databases. Is there anything we have to do to
>> install it and make sure it doesn't overwrite or delete the MSDE
>> database?
>>
>> TIA,
>> Clayton|||I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches.
Simple backup/restore. With MSDE i think u can too, backup that db and
restore to MSSQL 2005. How i understand MSDE is some as MSSQL with some
restrictions on db size,replications etc. All who run un MSDE must run
un MSSQL. I have few msde servers who replicating with MSSQL, sometimes
i need open archive of these msde databases, i do this on MSSQL without
problems.
Sry my poor english
Andris
Clayton Sutton wrote:
> An old app. that one dept. has been using for years was running on MSDE.
> Now they are moving to a new program that uses MSSQL 2000/2005. However,
> the old data is going to stay in the MSDE database (unless that dept. wants
> to pay someone to do a data export/import into MSSQL). I just wanted to
> make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE
> and all of the old data therein.
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>Hey everyone,
>>We are running MSDE on a Windows 200 server and it has data in it. What
>>I would like to know is can we also install MSSQL 2005 on that server and
>>have assess to both databases. Is there anything we have to do to
>>install it and make sure it doesn't overwrite or delete the MSDE
>>database?
>>
>>TIA,
>>Clayton
>
>|||Hey Andris,
First thing, your english is fine. Don't ever apologize for that. Truth be
told, I can't spell :).
Backing up MSDE is a little tricky. Most backup software doesn't have a
connector for MSDE so backing up and restore becomes a little harder.
The command line command to back one up is:
C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk ='c:\mssql7\backup\dbname.bak'"
It took me forever to find that command, and I don't know what the command
is to restore it.
Clayton
"Andris" <spameris@.gmail.com> wrote in message
news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches. Simple
>backup/restore. With MSDE i think u can too, backup that db and restore to
>MSSQL 2005. How i understand MSDE is some as MSSQL with some restrictions
>on db size,replications etc. All who run un MSDE must run un MSSQL. I have
>few msde servers who replicating with MSSQL, sometimes i need open archive
>of these msde databases, i do this on MSSQL without problems.
> Sry my poor english
> Andris
> Clayton Sutton wrote:
>> An old app. that one dept. has been using for years was running on MSDE.
>> Now they are moving to a new program that uses MSSQL 2000/2005. However,
>> the old data is going to stay in the MSDE database (unless that dept.
>> wants to pay someone to do a data export/import into MSSQL). I just
>> wanted to make sure installing MSSQL on the same system as MSDE didn't
>> wipe out MSDE and all of the old data therein.
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message
>> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>Hey everyone,
>>We are running MSDE on a Windows 200 server and it has data in it. What
>>I would like to know is can we also install MSSQL 2005 on that server
>>and have assess to both databases. Is there anything we have to do to
>>install it and make sure it doesn't overwrite or delete the MSDE
>>database?
>>
>>TIA,
>>Clayton
>>|||For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server 2000
(the MSDE info), you can download a copy of Books Online (BOL) at
http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en.
Using the example syntax you provided, it would probably be something like:
osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM
DISK='c:\mssql7\backup\dbname.bak'"
Note, however, that I haven't tested that. :-)
--
Sincerely,
Steve Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clayton Sutton" <none@.none.com> wrote in message
news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
> Hey Andris,
> First thing, your english is fine. Don't ever apologize for that. Truth
> be told, I can't spell :).
> Backing up MSDE is a little tricky. Most backup software doesn't have a
> connector for MSDE so backing up and restore becomes a little harder.
> The command line command to back one up is:
> C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk => 'c:\mssql7\backup\dbname.bak'"
> It took me forever to find that command, and I don't know what the command
> is to restore it.
>
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches. Simple
>>backup/restore. With MSDE i think u can too, backup that db and restore to
>>MSSQL 2005. How i understand MSDE is some as MSSQL with some restrictions
>>on db size,replications etc. All who run un MSDE must run un MSSQL. I have
>>few msde servers who replicating with MSSQL, sometimes i need open archive
>>of these msde databases, i do this on MSSQL without problems.
>> Sry my poor english
>> Andris
>> Clayton Sutton wrote:
>> An old app. that one dept. has been using for years was running on MSDE.
>> Now they are moving to a new program that uses MSSQL 2000/2005.
>> However, the old data is going to stay in the MSDE database (unless that
>> dept. wants to pay someone to do a data export/import into MSSQL). I
>> just wanted to make sure installing MSSQL on the same system as MSDE
>> didn't wipe out MSDE and all of the old data therein.
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message
>> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>Hey everyone,
>>We are running MSDE on a Windows 200 server and it has data in it.
>>What I would like to know is can we also install MSSQL 2005 on that
>>server and have assess to both databases. Is there anything we have to
>>do to install it and make sure it doesn't overwrite or delete the MSDE
>>database?
>>
>>TIA,
>>Clayton
>>
>|||Hey Steve,
Would that restore the DB to MSDE only. What if you wanted to restore it
into MSSQL 2000 or 2005? That's really what we are talking about, how to
move from MSDE to MSSQL 2000/2005. Get the data out of MSDE and into MSSQL.
Clayton
"Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in message
news:uIP9O6QdGHA.1436@.TK2MSFTNGP05.phx.gbl...
> For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
> http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server
> 2000 (the MSDE info), you can download a copy of Books Online (BOL) at
> http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en.
> Using the example syntax you provided, it would probably be something
> like:
> osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM
> DISK='c:\mssql7\backup\dbname.bak'"
> Note, however, that I haven't tested that. :-)
> --
> Sincerely,
> Steve Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clayton Sutton" <none@.none.com> wrote in message
> news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
>> Hey Andris,
>> First thing, your english is fine. Don't ever apologize for that. Truth
>> be told, I can't spell :).
>> Backing up MSDE is a little tricky. Most backup software doesn't have a
>> connector for MSDE so backing up and restore becomes a little harder.
>> The command line command to back one up is:
>> C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk =>> 'c:\mssql7\backup\dbname.bak'"
>> It took me forever to find that command, and I don't know what the
>> command is to restore it.
>>
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message
>> news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches.
>>Simple backup/restore. With MSDE i think u can too, backup that db and
>>restore to MSSQL 2005. How i understand MSDE is some as MSSQL with some
>>restrictions on db size,replications etc. All who run un MSDE must run un
>>MSSQL. I have few msde servers who replicating with MSSQL, sometimes i
>>need open archive of these msde databases, i do this on MSSQL without
>>problems.
>> Sry my poor english
>> Andris
>> Clayton Sutton wrote:
>> An old app. that one dept. has been using for years was running on
>> MSDE. Now they are moving to a new program that uses MSSQL 2000/2005.
>> However, the old data is going to stay in the MSDE database (unless
>> that dept. wants to pay someone to do a data export/import into MSSQL).
>> I just wanted to make sure installing MSSQL on the same system as MSDE
>> didn't wipe out MSDE and all of the old data therein.
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message
>> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>Hey everyone,
>>We are running MSDE on a Windows 200 server and it has data in it.
>>What I would like to know is can we also install MSSQL 2005 on that
>>server and have assess to both databases. Is there anything we have
>>to do to install it and make sure it doesn't overwrite or delete the
>>MSDE database?
>>
>>TIA,
>>Clayton
>>
>|||MSDE is SQL Server. So you can both attach and restore an MSDE 2000 database into SQL Server 2000 or
2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Clayton" <none@.none.com> wrote in message news:8GV8g.100380$JV1.10779@.fe05.news.easynews.com...
> Hey Steve,
> Would that restore the DB to MSDE only. What if you wanted to restore it into MSSQL 2000 or 2005?
> That's really what we are talking about, how to move from MSDE to MSSQL 2000/2005. Get the data
> out of MSDE and into MSSQL.
>
> Clayton
>
> "Steve Dybing [MSFT]" <steve.dybing@.online.microsoft.com> wrote in message
> news:uIP9O6QdGHA.1436@.TK2MSFTNGP05.phx.gbl...
>> For the RESTORE syntax, you can see the SQL Server 2005 RESTORE syntax at
>> http://msdn2.microsoft.com/en-us/library/ms186858.aspx. For SQL Server 2000 (the MSDE info), you
>> can download a copy of Books Online (BOL) at
>> http://www.microsoft.com/downloads/details.aspx?FamilyID=a6f79cb1-a420-445f-8a4b-bd77a7da194b&DisplayLang=en.
>> Using the example syntax you provided, it would probably be something like:
>> osql -Usa -P -n -Q "RESTORE DATABASE dbname FROM DISK='c:\mssql7\backup\dbname.bak'"
>> Note, however, that I haven't tested that. :-)
>> --
>> Sincerely,
>> Steve Dybing
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> "Clayton Sutton" <none@.none.com> wrote in message
>> news:2mH8g.471159$7i1.118830@.fe06.news.easynews.com...
>> Hey Andris,
>> First thing, your english is fine. Don't ever apologize for that. Truth be told, I can't spell
>> :).
>> Backing up MSDE is a little tricky. Most backup software doesn't have a connector for MSDE so
>> backing up and restore becomes a little harder.
>> The command line command to back one up is:
>> C:\MSSQL7\Binn>osql -Usa -P -n -Q "Backup Database dbname To Disk =>> 'c:\mssql7\backup\dbname.bak'"
>> It took me forever to find that command, and I don't know what the command is to restore it.
>>
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message news:%23sZUlTNdGHA.4108@.TK2MSFTNGP03.phx.gbl...
>>I just migrated from MSSQL 7 to MSSQL 2005, whithout big headaches. Simple backup/restore. With
>>MSDE i think u can too, backup that db and restore to MSSQL 2005. How i understand MSDE is some
>>as MSSQL with some restrictions on db size,replications etc. All who run un MSDE must run un
>>MSSQL. I have few msde servers who replicating with MSSQL, sometimes i need open archive of
>>these msde databases, i do this on MSSQL without problems.
>> Sry my poor english
>> Andris
>> Clayton Sutton wrote:
>> An old app. that one dept. has been using for years was running on MSDE. Now they are moving
>> to a new program that uses MSSQL 2000/2005. However, the old data is going to stay in the MSDE
>> database (unless that dept. wants to pay someone to do a data export/import into MSSQL). I
>> just wanted to make sure installing MSSQL on the same system as MSDE didn't wipe out MSDE and
>> all of the old data therein.
>>
>> Clayton
>>
>> "Andris" <spameris@.gmail.com> wrote in message news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>>Just interesting, why you do not want a run both databases on sql 2005?
>>Andris
>>Clayton Sutton wrote:
>>>Hey everyone,
>>>
>>>We are running MSDE on a Windows 200 server and it has data in it. What I would like to know
>>>is can we also install MSSQL 2005 on that server and have assess to both databases. Is there
>>>anything we have to do to install it and make sure it doesn't overwrite or delete the MSDE
>>>database?
>>>
>>>
>>>TIA,
>>>
>>>Clayton
>>
>>
>|||From your post it sounds like you believe that MSSQL and MSDE are two
different database formats. They are not. MSDE is merely a scaled-down
version of SQL Server, and the file formats are identical.
I, personally, develop in MSDE on my development machine, and then I make
changes to the live database which is running on SQL Server. When I need a
new copy of the data, I download a backup file from the SQL Server database
and run it in my MSDE. The two formats are identical.
Thus, while installing MSSQL might create conflicts with running MSDE, the
*data itself* will remain untouched. Since your MSDE data is in SQL 7
format, there may be issues with running your data on a later version of
MSSQL, but those should be able to be resolved.
"Clayton Sutton" <none@.none.com> wrote in message
news:xIt8g.391355$4P2.48017@.fe03.news.easynews.com...
> An old app. that one dept. has been using for years was running on MSDE.
> Now they are moving to a new program that uses MSSQL 2000/2005. However,
> the old data is going to stay in the MSDE database (unless that dept.
> wants to pay someone to do a data export/import into MSSQL). I just
> wanted to make sure installing MSSQL on the same system as MSDE didn't
> wipe out MSDE and all of the old data therein.
>
> Clayton
>
> "Andris" <spameris@.gmail.com> wrote in message
> news:Ocnzq1BdGHA.1272@.TK2MSFTNGP03.phx.gbl...
>> Just interesting, why you do not want a run both databases on sql 2005?
>> Andris
>> Clayton Sutton wrote:
>> Hey everyone,
>> We are running MSDE on a Windows 200 server and it has data in it. What
>> I would like to know is can we also install MSSQL 2005 on that server
>> and have assess to both databases. Is there anything we have to do to
>> install it and make sure it doesn't overwrite or delete the MSDE
>> database?
>>
>> TIA,
>> Clayton
>
Subscribe to:
Posts (Atom)