All,
looking to distribute MSDE with my ASP.NET app... looking for two pieces:
1) Is there a way to install MSDE with a DB already attached? I want to
install MSDE and then attach a DB, but attaching has to come after a
reboot(to start after services restart), and I would rather do it all at the
same time...
2) Good Freeware/Almost-freeware MSDE manager I can redistribute with my app
for the client
MTIA
wardeaux
> 2) Good Freeware/Almost-freeware MSDE manager I can redistribute with my
app
> for the client
http://www.aspfaq.com/2442
http://www.aspfaq.com/
(Reverse address to reply.)
|||1) Nope. You don't have to reboot the computer when you install MSDE though,
strictly speaking.
2) SQL Server Web Data Administrator:
http://www.microsoft.com/downloads/d...displaylang=en
Jacco Schalkwijk
SQL Server MVP
"Wardeaux" <wardeaux@.bellsouth.net> wrote in message
news:e10zJ72jEHA.3196@.TK2MSFTNGP10.phx.gbl...
> All,
> looking to distribute MSDE with my ASP.NET app... looking for two pieces:
> 1) Is there a way to install MSDE with a DB already attached? I want to
> install MSDE and then attach a DB, but attaching has to come after a
> reboot(to start after services restart), and I would rather do it all at
> the
> same time...
> 2) Good Freeware/Almost-freeware MSDE manager I can redistribute with my
> app
> for the client
> MTIA
> wardeaux
>
|||You don't necessarily need to reboot after installing. To start MSDE after
installing, just run "net start mssql$instancename" (if installing as a
named instance) or use scm.exe. You may want to start SQL Server Agent
also.
Distribute your database's .mdf and .ldf files and attach them using
osql.exe to execute the sp_attach_db stored procedure.
"Wardeaux" <wardeaux@.bellsouth.net> wrote in message
news:e10zJ72jEHA.3196@.TK2MSFTNGP10.phx.gbl...
> All,
> looking to distribute MSDE with my ASP.NET app... looking for two
pieces:
> 1) Is there a way to install MSDE with a DB already attached? I want to
> install MSDE and then attach a DB, but attaching has to come after a
> reboot(to start after services restart), and I would rather do it all at
the
> same time...
> 2) Good Freeware/Almost-freeware MSDE manager I can redistribute with my
app
> for the client
> MTIA
> wardeaux
>
sql
Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts
Wednesday, March 28, 2012
new to .net MSDE (database) question ?
Hi, I am new to .net, I installed .net sdk and framework.
now I downloaded MSDE and installed it, I got this directory : C:\MSDERelA
but when I double click in the setup file nothing happened, please help me on what should I do .
thanksMay be missing parameters.
now I downloaded MSDE and installed it, I got this directory : C:\MSDERelA
but when I double click in the setup file nothing happened, please help me on what should I do .
thanksMay be missing parameters.
Open the ReadmeMSDE2000A.htm and read under the '3.4.4 MSDE 2000 Release A Installation Examples'.
New Tables and Stored procedures are saving as System Tables
When I try to create a new table/stored procedure, MSDE is saving it as
system table/procedure. And this is happening to all the databases on that
instance.
I checked the sysobjects table. The new tables are saved as Type 'U'.
But their status is in -ve nos.
What I can do to fix that?
Hi
You should not rely on using the "FOR MS USE" objects/columns. What does
OBJECTPROPERTY(id,'IsSystemTable') return?
John
"Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
news:45F7565B-FC35-437E-88CC-30E896875DF0@.microsoft.com...
> When I try to create a new table/stored procedure, MSDE is saving it as
> system table/procedure. And this is happening to all the databases on that
> instance.
> I checked the sysobjects table. The new tables are saved as Type 'U'.
> But their status is in -ve nos.
> What I can do to fix that?
>
>
system table/procedure. And this is happening to all the databases on that
instance.
I checked the sysobjects table. The new tables are saved as Type 'U'.
But their status is in -ve nos.
What I can do to fix that?
Hi
You should not rely on using the "FOR MS USE" objects/columns. What does
OBJECTPROPERTY(id,'IsSystemTable') return?
John
"Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
news:45F7565B-FC35-437E-88CC-30E896875DF0@.microsoft.com...
> When I try to create a new table/stored procedure, MSDE is saving it as
> system table/procedure. And this is happening to all the databases on that
> instance.
> I checked the sysobjects table. The new tables are saved as Type 'U'.
> But their status is in -ve nos.
> What I can do to fix that?
>
>
Monday, March 26, 2012
New Tables and Stored procedures are saving as System Tables
When I try to create a new table/stored procedure, MSDE is saving it as
system table/procedure. And this is happening to all the databases on that
instance.
I checked the sysobjects table. The new tables are saved as Type 'U'.
But their status is in -ve nos.
What I can do to fix that?Hi
You should not rely on using the "FOR MS USE" objects/columns. What does
OBJECTPROPERTY(id,'IsSystemTable') return?
John
"Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
news:45F7565B-FC35-437E-88CC-30E896875DF0@.microsoft.com...
> When I try to create a new table/stored procedure, MSDE is saving it as
> system table/procedure. And this is happening to all the databases on that
> instance.
> I checked the sysobjects table. The new tables are saved as Type 'U'.
> But their status is in -ve nos.
> What I can do to fix that?
>
>
system table/procedure. And this is happening to all the databases on that
instance.
I checked the sysobjects table. The new tables are saved as Type 'U'.
But their status is in -ve nos.
What I can do to fix that?Hi
You should not rely on using the "FOR MS USE" objects/columns. What does
OBJECTPROPERTY(id,'IsSystemTable') return?
John
"Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
news:45F7565B-FC35-437E-88CC-30E896875DF0@.microsoft.com...
> When I try to create a new table/stored procedure, MSDE is saving it as
> system table/procedure. And this is happening to all the databases on that
> instance.
> I checked the sysobjects table. The new tables are saved as Type 'U'.
> But their status is in -ve nos.
> What I can do to fix that?
>
>
Friday, March 23, 2012
NEW SQL Server Release`
Check this out
this is the replacement for MSDE 2000
SQL Server 2005 Express Edition (http://lab.msdn.microsoft.com/express/sql/default.aspx)
Top 10 cool things about SQL Server Express Edition (http://lab.msdn.microsoft.com/express/sql/top10/default.aspx)
SQL Server Express Books Online (http://www.microsoft.com/downloads/details.aspx?FamilyId=2ADBC1A8-AE5C-497D-B584-EAB6719300CD&displaylang=en)
by the way if you follow the first link, you will find a pretty accurate photo of rdjabarov...Check this out
you will find a pretty accurate photo of rdjabarov...
Looks pretty nice and decent just like the Express Edition. Where he's from by the way, USA!!|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?|||Hey now, I'm from Ala-freaking-bama|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?
i'm just kidding
but on further reflection he kind of looks like fabian pascal.
Pat can verify that for us because as we all know, he's fabian's best friend.|||Do you really believe that I think that way?..Well, I DO love Texas, but I am ready for a change (ideally would be to move without my kids knowing where to :D )|||Anyone else think that CLR is a bunch of nonsense?|||Anyone else think that CLR is a bunch of nonsense?
I think it's VERY neat. I also think that this will force some hard core production DBA's to have a hard look at themselves and see if the career they've chosen is what they want to continue pursuing. Personally, I am happy with a definition that is given to me, - hybrid DBA! And the direction the job description is taking is where I am at now.|||Pat can verify that for us because as we all know, he's fabian's best friend.It's good to be loved, isn't it? Actually, I've never met Fabian in person, or even seen a picture from a reliable source, so I'm no authority there. It's hard to imagine that I've never seen anyone that loves me so, isn't it?
-PatP|||Anyone else think that CLR is a bunch of nonsense?Not really, I think that the CLR brings a lot of interesting benefits, but it brings some new risks in the baggage with it.
The benefits are basically the ones that UCSD promised with the p-machine and Java didn't quite deliver with their virtual machine. A standard, more or less hardware independant virtual machine. One code base for many platforms. One target for many compilers, which allows much better tools to evolve because the economies of scale kick in much sooner.
The big risks seem to be that once something makes it into the runtime, who will ensure that it makes sense for it to stay there as it evolves. Many things that make perfect sense on the desktop (or even handheld) are a positive liability on a server!
It is a two edged sword. It brings many benefits, but at a significant cost.
-PatP|||I think it's VERY neat.
Why? And yes, PROD DBA's who sit there waiting for an alert...sure...but someones got to do that...and I'm glad it's not me...not sure if they even know what a sproc is...let alone a trigger...
And what can you do with "External Procedures" (CLR) that you can't do with T-SQL or it's extensions?
CLR is just more overhead...
And I'd love to see what they mean by Extensive XML support...
What? Did they add Relational extenders to XML?|||Well, I've run to the rescue of "External Procedures" via sp_oaxxx. You're write, the same thing can be accomplished by T-SQL, but the final choice is based on many factors. I prefer to use a tool for a task that is designed to do that task. Of course I can create a file using T-SQL, but if there is a better way to do the same thing (Scripting.FileSystemObject) I'd pick that one.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)|||I think Pat summed it up pretty well. There are some things that the CLR will just do better. There's also a LOT of risk if it's used wrong. The XML thing actually worries me more then the CLR though. It's harking back to the days of hierarchial design and promising "extensibility". I have a feeling we'll end up regretting the degradation of a relational environment to cater to the desires of a shortcut "extend into anything without considering the consequences" world. Oh well....rant off.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)
Right on, man, right on!
this is the replacement for MSDE 2000
SQL Server 2005 Express Edition (http://lab.msdn.microsoft.com/express/sql/default.aspx)
Top 10 cool things about SQL Server Express Edition (http://lab.msdn.microsoft.com/express/sql/top10/default.aspx)
SQL Server Express Books Online (http://www.microsoft.com/downloads/details.aspx?FamilyId=2ADBC1A8-AE5C-497D-B584-EAB6719300CD&displaylang=en)
by the way if you follow the first link, you will find a pretty accurate photo of rdjabarov...Check this out
you will find a pretty accurate photo of rdjabarov...
Looks pretty nice and decent just like the Express Edition. Where he's from by the way, USA!!|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?|||Hey now, I'm from Ala-freaking-bama|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?
i'm just kidding
but on further reflection he kind of looks like fabian pascal.
Pat can verify that for us because as we all know, he's fabian's best friend.|||Do you really believe that I think that way?..Well, I DO love Texas, but I am ready for a change (ideally would be to move without my kids knowing where to :D )|||Anyone else think that CLR is a bunch of nonsense?|||Anyone else think that CLR is a bunch of nonsense?
I think it's VERY neat. I also think that this will force some hard core production DBA's to have a hard look at themselves and see if the career they've chosen is what they want to continue pursuing. Personally, I am happy with a definition that is given to me, - hybrid DBA! And the direction the job description is taking is where I am at now.|||Pat can verify that for us because as we all know, he's fabian's best friend.It's good to be loved, isn't it? Actually, I've never met Fabian in person, or even seen a picture from a reliable source, so I'm no authority there. It's hard to imagine that I've never seen anyone that loves me so, isn't it?
-PatP|||Anyone else think that CLR is a bunch of nonsense?Not really, I think that the CLR brings a lot of interesting benefits, but it brings some new risks in the baggage with it.
The benefits are basically the ones that UCSD promised with the p-machine and Java didn't quite deliver with their virtual machine. A standard, more or less hardware independant virtual machine. One code base for many platforms. One target for many compilers, which allows much better tools to evolve because the economies of scale kick in much sooner.
The big risks seem to be that once something makes it into the runtime, who will ensure that it makes sense for it to stay there as it evolves. Many things that make perfect sense on the desktop (or even handheld) are a positive liability on a server!
It is a two edged sword. It brings many benefits, but at a significant cost.
-PatP|||I think it's VERY neat.
Why? And yes, PROD DBA's who sit there waiting for an alert...sure...but someones got to do that...and I'm glad it's not me...not sure if they even know what a sproc is...let alone a trigger...
And what can you do with "External Procedures" (CLR) that you can't do with T-SQL or it's extensions?
CLR is just more overhead...
And I'd love to see what they mean by Extensive XML support...
What? Did they add Relational extenders to XML?|||Well, I've run to the rescue of "External Procedures" via sp_oaxxx. You're write, the same thing can be accomplished by T-SQL, but the final choice is based on many factors. I prefer to use a tool for a task that is designed to do that task. Of course I can create a file using T-SQL, but if there is a better way to do the same thing (Scripting.FileSystemObject) I'd pick that one.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)|||I think Pat summed it up pretty well. There are some things that the CLR will just do better. There's also a LOT of risk if it's used wrong. The XML thing actually worries me more then the CLR though. It's harking back to the days of hierarchial design and promising "extensibility". I have a feeling we'll end up regretting the degradation of a relational environment to cater to the desires of a shortcut "extend into anything without considering the consequences" world. Oh well....rant off.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)
Right on, man, right on!
Monday, March 19, 2012
New server registration error
Hi, I've just installed MSDE 2000 Release A on a Windows NT Server 4.0 w/SP6. I'm on a WinXP machine and I've installed the Enterprise Manager, and am trying to register a new server registration. However, I'm getting the error: Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection. I've made sure that both the client and server are using TCP/IP for the protocol list, and I've tried using the physical server's name and it's IP address to register, but keep getting the same error. Thanks for the help.How are you authentacating? Try a search before posting.
http://www.dbforums.com/t525129.html
or
http://search.msn.com/pass/results.asp?RS=CHECKED&FORM=MSNH&v=1&&q=Login+failed+for+user+%27sa%27.+&cp=1252|||I was trying to authenticate via SQL Authentication. I did try searching, and nothing I found seemed to pertain to my situation. But I fixed the problem, so if anyone wants to know, I used Windows authentication to register the server, then I right-clicked on the server, chose properties, and went to the security tab. In there, it was checked to use "Windows only" under the Authentication section. I changed it to "SQL Server and Windows", restarted the SQL service, deleted my Windows SQL registration. Then I was able to successfully register my SQL server using SQL Authentication!
http://www.dbforums.com/t525129.html
or
http://search.msn.com/pass/results.asp?RS=CHECKED&FORM=MSNH&v=1&&q=Login+failed+for+user+%27sa%27.+&cp=1252|||I was trying to authenticate via SQL Authentication. I did try searching, and nothing I found seemed to pertain to my situation. But I fixed the problem, so if anyone wants to know, I used Windows authentication to register the server, then I right-clicked on the server, chose properties, and went to the security tab. In there, it was checked to use "Windows only" under the Authentication section. I changed it to "SQL Server and Windows", restarted the SQL service, deleted my Windows SQL registration. Then I was able to successfully register my SQL server using SQL Authentication!
Monday, March 12, 2012
New MSDE Installation
What is the proper way to install a new MSDE Installation?
MSDE Release A then SP4
or
Can SP4 be used for a new installation on a PC?
hi,
topherdel wrote:
> What is the proper way to install a new MSDE Installation?
> MSDE Release A then SP4
> or
> Can SP4 be used for a new installation on a PC?
you can go both way... but directly installing sp4 will result in lower
installation time...
just a caveat... at the moment is not clear to me if it's legal for non
entitled persons (people not owing a legal copy of a product entiteling for
MSDE sp4 new installation use) to use sp4 package to directly install new
instances... but it is legal to use that package to upgrade MSDE Rel. A
instances to sp4...
I've been told a refresh of MSDE Rel.A updated at sp4 level will be
available, but no idea for the time frame...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The rules seem to change with each release as to who can use it and who cannot.
"Andrea Montanari" wrote:
> hi,
> topherdel wrote:
> you can go both way... but directly installing sp4 will result in lower
> installation time...
> just a caveat... at the moment is not clear to me if it's legal for non
> entitled persons (people not owing a legal copy of a product entiteling for
> MSDE sp4 new installation use) to use sp4 package to directly install new
> instances... but it is legal to use that package to upgrade MSDE Rel. A
> instances to sp4...
> I've been told a refresh of MSDE Rel.A updated at sp4 level will be
> available, but no idea for the time frame...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
MSDE Release A then SP4
or
Can SP4 be used for a new installation on a PC?
hi,
topherdel wrote:
> What is the proper way to install a new MSDE Installation?
> MSDE Release A then SP4
> or
> Can SP4 be used for a new installation on a PC?
you can go both way... but directly installing sp4 will result in lower
installation time...
just a caveat... at the moment is not clear to me if it's legal for non
entitled persons (people not owing a legal copy of a product entiteling for
MSDE sp4 new installation use) to use sp4 package to directly install new
instances... but it is legal to use that package to upgrade MSDE Rel. A
instances to sp4...
I've been told a refresh of MSDE Rel.A updated at sp4 level will be
available, but no idea for the time frame...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The rules seem to change with each release as to who can use it and who cannot.
"Andrea Montanari" wrote:
> hi,
> topherdel wrote:
> you can go both way... but directly installing sp4 will result in lower
> installation time...
> just a caveat... at the moment is not clear to me if it's legal for non
> entitled persons (people not owing a legal copy of a product entiteling for
> MSDE sp4 new installation use) to use sp4 package to directly install new
> instances... but it is legal to use that package to upgrade MSDE Rel. A
> instances to sp4...
> I've been told a refresh of MSDE Rel.A updated at sp4 level will be
> available, but no idea for the time frame...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
new MSDE install fails with "instance name specified is invalid"
I am trying to put SQL Server 2000 and MSDE on same local machine. I install
ed 2000 Developer (from VS Tools for Office)using "typical" install level, u
sing the LocalSystem Account, so no password required. When I run C:\sql2ksp
3\MSDE\setup.exe (generated
by Office 2003 disk), the first thing that happens is dialog box that says "
instance name specified is invalid" and the setup is cancelled. When I tried
to do the MSDE install before the 2000, I got a "Strong SA password is requ
ired - use SAPWD switch to
supply the same", so I installed the 2000 and then came back to try MSDE, if
only because I couldn't figure out how to get Online Books going to find ou
t about how to supply SAPWD. There is no other instance of 2000, and none of
MSDE, on the machine. I t
hought the 2000 instance was unnamed. (?)
I am an almost complete rookie about SQL Server. Any help on instance name w
ould be appreciated, or the SAPWD which may be waiting for me. Thanks !hi Bob,
"Bob P." <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:111B62D3-B753-4A78-88BD-7309173DFE4F@.microsoft.com...
> I am trying to put SQL Server 2000 and MSDE on same local machine. I
installed 2000
> Developer (from VS Tools for Office)using "typical" install level, using
the LocalSystem
>Account, so no password required. When I run C:\sql2ksp3\MSDE\setup.exe
(generated by
>Office 2003 disk), the first thing that happens is dialog box that says
"instance name
>specified is invalid" and the setup is cancelled. When I tried to do the
MSDE install before
>the 2000, I got a "Strong SA password is required - use SAPWD switch to
supply the
>same", so I installed the 2000 and then came back to try MSDE, if only
because I couldn't
>figure out how to get Online Books going to find out about how to supply
SAPWD. There is
>no other instance of 2000, and none of MSDE, on the machine. I thought the
2000 instance
>was unnamed. (?)
> I am an almost complete rookie about SQL Server. Any help on instance name
would be
> appreciated, or the SAPWD which may be waiting for me. Thanks !
the first SQL Server instance you installed hase become the default instance
becouse you did not provide instance name...
in order to install other SQL Server and/or MSDE instancese, they must be
"named" instances...
please see
http://msdn.microsoft.com/library/d...
4xl.asp
for further info about all parameters accepted by the setup.exe installer
bootstrap of MSDE...
you can download Books On Line for free from
http://www.microsoft.com/sql/techin.../2000/books.asp
hth
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||See the sp3 readme for the valid options for setup.
814130 INF: How to Secure Network Connectivity for SQL Server 2000 Local
http://support.microsoft.com/?id=814130
829925 Additions to the SQL Server 2000 Desktop Engine (MSDE) Release A
http://support.microsoft.com/?id=829925
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
ed 2000 Developer (from VS Tools for Office)using "typical" install level, u
sing the LocalSystem Account, so no password required. When I run C:\sql2ksp
3\MSDE\setup.exe (generated
by Office 2003 disk), the first thing that happens is dialog box that says "
instance name specified is invalid" and the setup is cancelled. When I tried
to do the MSDE install before the 2000, I got a "Strong SA password is requ
ired - use SAPWD switch to
supply the same", so I installed the 2000 and then came back to try MSDE, if
only because I couldn't figure out how to get Online Books going to find ou
t about how to supply SAPWD. There is no other instance of 2000, and none of
MSDE, on the machine. I t
hought the 2000 instance was unnamed. (?)
I am an almost complete rookie about SQL Server. Any help on instance name w
ould be appreciated, or the SAPWD which may be waiting for me. Thanks !hi Bob,
"Bob P." <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:111B62D3-B753-4A78-88BD-7309173DFE4F@.microsoft.com...
> I am trying to put SQL Server 2000 and MSDE on same local machine. I
installed 2000
> Developer (from VS Tools for Office)using "typical" install level, using
the LocalSystem
>Account, so no password required. When I run C:\sql2ksp3\MSDE\setup.exe
(generated by
>Office 2003 disk), the first thing that happens is dialog box that says
"instance name
>specified is invalid" and the setup is cancelled. When I tried to do the
MSDE install before
>the 2000, I got a "Strong SA password is required - use SAPWD switch to
supply the
>same", so I installed the 2000 and then came back to try MSDE, if only
because I couldn't
>figure out how to get Online Books going to find out about how to supply
SAPWD. There is
>no other instance of 2000, and none of MSDE, on the machine. I thought the
2000 instance
>was unnamed. (?)
> I am an almost complete rookie about SQL Server. Any help on instance name
would be
> appreciated, or the SAPWD which may be waiting for me. Thanks !
the first SQL Server instance you installed hase become the default instance
becouse you did not provide instance name...
in order to install other SQL Server and/or MSDE instancese, they must be
"named" instances...
please see
http://msdn.microsoft.com/library/d...
4xl.asp
for further info about all parameters accepted by the setup.exe installer
bootstrap of MSDE...
you can download Books On Line for free from
http://www.microsoft.com/sql/techin.../2000/books.asp
hth
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.6.0 - DbaMgr ver 0.52.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||See the sp3 readme for the valid options for setup.
814130 INF: How to Secure Network Connectivity for SQL Server 2000 Local
http://support.microsoft.com/?id=814130
829925 Additions to the SQL Server 2000 Desktop Engine (MSDE) Release A
http://support.microsoft.com/?id=829925
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Friday, March 9, 2012
new installation question
I've installed MSDE on a W2000 machine and want to set up an ODBC connection to it from an XP machine using an IP address and specifying a port. How do I determine the login and password I need to use to make the connection
Thanks...Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/default.aspx?scid=kb;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison|||If you require SQL authentication, you have to specify
following option for setup.exe while installing MSDE.
Setup.exe SECURITYMODE=SQL SAPWD=<password>
Shrikant Patil
MCDBA
>--Original Message--
>I've installed MSDE on a W2000 machine and want to set
up an ODBC connection to it from an XP machine using an
IP address and specifying a port. How do I determine the
login and password I need to use to make the connection?
>Thanks...
>.
>
Thanks...Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/default.aspx?scid=kb;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison|||If you require SQL authentication, you have to specify
following option for setup.exe while installing MSDE.
Setup.exe SECURITYMODE=SQL SAPWD=<password>
Shrikant Patil
MCDBA
>--Original Message--
>I've installed MSDE on a W2000 machine and want to set
up an ODBC connection to it from an XP machine using an
IP address and specifying a port. How do I determine the
login and password I need to use to make the connection?
>Thanks...
>.
>
new installation question
I've installed MSDE on a W2000 machine and want to set up an ODBC connection to it from an XP machine using an IP address and specifying a port. How do I determine the login and password I need to use to make the connection?
Thanks...
Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/default...b;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...
|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison
Thanks...
Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/default...b;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...
|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison
new installation question
I've installed MSDE on a W2000 machine and want to set up an ODBC connection
to it from an XP machine using an IP address and specifying a port. How do
I determine the login and password I need to use to make the connection?
Thanks...Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/defaul...kb;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison
to it from an XP machine using an IP address and specifying a port. How do
I determine the login and password I need to use to make the connection?
Thanks...Hi,
First , you have to enable TCP/IP protocol from MDE server.
From command prompt of server execute (Server Network Utility) :-
svrnetcn.exe
Here, You can enable the TCPIP protocol
By default MSDE only support Windows authentication. So try creating an ODBC
using a Domain id. Ensure that domain user has got access to SQL Server.
By default users of local administrator group will have access. Have a look
into books online for the below procedures to give preevilages:-
1. sp_grantlogin
2. sp_grantdbaccess
Have a look into below link to identify for connectivity issues:-
http://support.microsoft.com/defaul...kb;en-us;827422
Thanks
Hari
MCDBA
"Jeff" <jstemper@.wi.rr.com> wrote in message
news:9DFDAD9E-49E7-4A04-8A0F-56BD4821EC36@.microsoft.com...
> I've installed MSDE on a W2000 machine and want to set up an ODBC
connection to it from an XP machine using an IP address and specifying a
port. How do I determine the login and password I need to use to make the
connection?
> Thanks...|||Jeff,
if you are using trusted security, then there won't be a requirement for a
login and password. If you are using SQL Server security, then you just need
to create a SQL Server login on MSDE and incorporate its details in the
connectionstring. I'm guessing here, but it may be that your question is
wider and you want to know generally about administering the MSDE
installation. SQL Server client tools from any other box could be used to
administer it. Just make sure that the box which is using the client tools
uses trusted security, and the windows login on this box is in the local
administrators group on the MSDE machine. To cheaply set this up, you could
use the Developer Edition to get the client tools. Some people talk about
using the Evaluation client tools although the legality of this is dubious -
you'd have to check this out with MS.
HTH,
Paul Ibison
Wednesday, March 7, 2012
New in MSDE, Please help!
Hi,
I am newbie in ASP.NET and MSDE arena. I understand that MSDE has no GUI and I need to have MSDE tools to work with it. I have already installed ASP.NET 1.1 and Microsoft.NET SDK 1.1 and MSDE in my Windown Professional 2000 PC and I have run and tested for .aspx and its working perfectly. But I want to use MSDE to create some database driven web applications.
Could you please help me how I can do that? BTW, I installed Microsoft SQL Web Data Administrator and its giving me SQLWebAdminStart.exe Application error and asking for debugging while opening the program. I am stranded what to do now?
I really appreciate your help.
regards,
Peter-Toronto
(Linux, PHP, MySQL)Hello Peter again,
I want to ask you which tools are you using to build your ASP.net application. If you'r using WebMAtrix project, then you can easly create your own database by going to Data Tab(located on the right section of the webmatrix page). Then go to "Aadd database connection". from there you can choose whether you want to create MSDE or Access databases. finally, you can go through the next steps to create your database. It is easy steps.
I hope it is clear now.
Subscribe to:
Posts (Atom)