My objective is to use Enterprise Manager to move (copy) my SQL db from the server to my windows desktop computer.
I downloaded MSDE and am having trouble installing it, no doubt because I do not understand the documentaion (ReadMeMSDE2000A.htm).
When I try to run setup, I get that message that says:
"A strong SA password is required for security reasons. Please use SAPWD switch to supply the same."
Considering my purpose, do I need a "strong" SA password? If not, how do I get around it? If yes, how do I set it up?
I am a Mac user so I have poor windows skills, please make it as painless as possible for me, thanks!
RonCreate 2 file in the same director with setup.exe
1. Setup.bat
setup.exe /settings Settings.ini /L*v C:/MSDELog.log
2. Settings.ini
[Options]
SAPWD=YourPassword
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\MSDE"
TARGETDIR="C:\MSDE"
Run the setup.bat|||I have tried your code and other code like that and in each case it fails. I keep getting this error message that says:
"The instance name specified is not valid."
Note that your code didn't even use the instance name.
In your code you use:
DATADIR="C:\MSDE"
TARGETDIR="C:\MSDE"
Actually on my C drive the folder is called MSDERela. I tried changing your code to indicate that and it still doesn't work. Same error message.
Any other suggestions? Thanks!|||I added the INSTANCENAME and added quote marks to some of the code and it seems to have worked. It produced a folder on my C drive wtih a number of files in it.
Now can someone tell me how to launch MSDE?
Now you know why I call myself SQL_Dummy!sql
Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts
Wednesday, March 28, 2012
Friday, March 23, 2012
Microsoft ODBC Sql server driver Communication Link Failure
I get the message Microsoft [ODBC Sql server driver]communication link failure error message in my VB 6 application with MSDE engine. This error does not happen often.
My connection string is as below.
"Provider=MSDASQL;Driver={SQL Server};Server=" & mSvrName & ";DATABASE=cnsClient;uid=uid;pwd=pwd"
Please help.Were you able to figure out a solution? It seems like a ODBC specific error more than a MSSQL one. I get the same error when trying execute queries against a DB2 database.
My connection string is as below.
"Provider=MSDASQL;Driver={SQL Server};Server=" & mSvrName & ";DATABASE=cnsClient;uid=uid;pwd=pwd"
Please help.Were you able to figure out a solution? It seems like a ODBC specific error more than a MSSQL one. I get the same error when trying execute queries against a DB2 database.
Microsoft MSDE
I am currently running Great Plains 7.5 on Pervasive.SQL SP3 using Windows
98. We are upgrading to Windows XP Pro and Microsoft MSDE.
Does it make a difference if I update MSDE first and then Windows XP or
should I update Windows XP first?
Thank you.
Bob,
I have found that it is a good practice to update your OS first then upgrade
any software(MSDE). If you have the luxury you should re install the OS and
bypass any upgrade paths. You will get a cleaner install of everything this
way and likely prevent any "ghost" bugs later on.
Hope this helps.
sql
98. We are upgrading to Windows XP Pro and Microsoft MSDE.
Does it make a difference if I update MSDE first and then Windows XP or
should I update Windows XP first?
Thank you.
Bob,
I have found that it is a good practice to update your OS first then upgrade
any software(MSDE). If you have the luxury you should re install the OS and
bypass any upgrade paths. You will get a cleaner install of everything this
way and likely prevent any "ghost" bugs later on.
Hope this helps.
sql
Microsoft MSDE
I am currently running Great Plains 7.5 on Pervasive.SQL SP3 using Windows
98. We are upgrading to Windows XP Pro and Microsoft MSDE.
Does it make a difference if I update MSDE first and then Windows XP or
should I update Windows XP first?
Thank you.Bob,
I have found that it is a good practice to update your OS first then upgrade
any software(MSDE). If you have the luxury you should re install the OS and
bypass any upgrade paths. You will get a cleaner install of everything this
way and likely prevent any "ghost" bugs later on.
Hope this helps.
98. We are upgrading to Windows XP Pro and Microsoft MSDE.
Does it make a difference if I update MSDE first and then Windows XP or
should I update Windows XP first?
Thank you.Bob,
I have found that it is a good practice to update your OS first then upgrade
any software(MSDE). If you have the luxury you should re install the OS and
bypass any upgrade paths. You will get a cleaner install of everything this
way and likely prevent any "ghost" bugs later on.
Hope this helps.
Wednesday, March 21, 2012
Microsoft Enterprise Manager cannot "see" an instance of Microsoft MSDE-SQL - Server
Hello,
i have following Problem:
i have created a new instance of Microsoft SQL - Server with MSDE and now i
want to connect to a database on this instance through a network.
But i do not "see" the instance ...
I have tested it with
- Enterprise Manager
- an Microsoft Access .adp - Project
- MSDE+ SQL-Server Management Tool
Also: The server is started, this was my first look up .....
Who can help me'
Thanks in the beginning ...
PeterHi
Have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;814130
and
http://support.microsoft.com/default.aspx?scid=kb;en-us;827204
Regards
Mike
"stundner@.oca.at" wrote:
> Hello,
> i have following Problem:
> i have created a new instance of Microsoft SQL - Server with MSDE and now i
> want to connect to a database on this instance through a network.
> But i do not "see" the instance ...
> I have tested it with
> - Enterprise Manager
> - an Microsoft Access .adp - Project
> - MSDE+ SQL-Server Management Tool
> Also: The server is started, this was my first look up .....
>
> Who can help me'
>
> Thanks in the beginning ...
> Peter
>
>
i have following Problem:
i have created a new instance of Microsoft SQL - Server with MSDE and now i
want to connect to a database on this instance through a network.
But i do not "see" the instance ...
I have tested it with
- Enterprise Manager
- an Microsoft Access .adp - Project
- MSDE+ SQL-Server Management Tool
Also: The server is started, this was my first look up .....
Who can help me'
Thanks in the beginning ...
PeterHi
Have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;814130
and
http://support.microsoft.com/default.aspx?scid=kb;en-us;827204
Regards
Mike
"stundner@.oca.at" wrote:
> Hello,
> i have following Problem:
> i have created a new instance of Microsoft SQL - Server with MSDE and now i
> want to connect to a database on this instance through a network.
> But i do not "see" the instance ...
> I have tested it with
> - Enterprise Manager
> - an Microsoft Access .adp - Project
> - MSDE+ SQL-Server Management Tool
> Also: The server is started, this was my first look up .....
>
> Who can help me'
>
> Thanks in the beginning ...
> Peter
>
>
Monday, March 12, 2012
Mgmt Studio
Can I manage MSDE databases in Management Studio? If not, how can I? How
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
Regards,
Gary BlakelyTry to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
Regards,
Gary BlakelyTry to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
Mgmt Studio
Can I manage MSDE databases in Management Studio? If not, how can I? How
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
--
Regards,
Gary BlakelyTry to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>|||Hi Gary,
SQL Server 2005 Management Studio totally supports attaching SQL Server
2000, MSDE2000 and SQL Express databases by using sp_detach_db/sp_attach_db
stored procedure.
Please try again via the following:
1. Connect to your MSDE instance, and run the following statement:
use master
go
exec sp_detach_db 'YourDatabaseName'
2. Connect to your SQL Server 2005 instance and run the following statement:
use master
go
exec sp_attach_db @.dbname='DatabaseName',
@.filename1 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test.mdf',
@.filename2 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test_log.ldf'
Could you please mail me (changliw@.microsoft.com) the SQL error logs and a
screenshot of the error message for further research?
By default, the error logs of SQL Server 2005 instance are located in
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG". You may check it
if there are multiple instances installed on your computer.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
--
Regards,
Gary BlakelyTry to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>|||Hi Gary,
SQL Server 2005 Management Studio totally supports attaching SQL Server
2000, MSDE2000 and SQL Express databases by using sp_detach_db/sp_attach_db
stored procedure.
Please try again via the following:
1. Connect to your MSDE instance, and run the following statement:
use master
go
exec sp_detach_db 'YourDatabaseName'
2. Connect to your SQL Server 2005 instance and run the following statement:
use master
go
exec sp_attach_db @.dbname='DatabaseName',
@.filename1 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test.mdf',
@.filename2 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test_log.ldf'
Could you please mail me (changliw@.microsoft.com) the SQL error logs and a
screenshot of the error message for further research?
By default, the error logs of SQL Server 2005 instance are located in
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG". You may check it
if there are multiple instances installed on your computer.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
Mgmt Studio
Can I manage MSDE databases in Management Studio? If not, how can I? How
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
Regards,
Gary Blakely
Try to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>
|||Hi Gary,
SQL Server 2005 Management Studio totally supports attaching SQL Server
2000, MSDE2000 and SQL Express databases by using sp_detach_db/sp_attach_db
stored procedure.
Please try again via the following:
1. Connect to your MSDE instance, and run the following statement:
use master
go
exec sp_detach_db 'YourDatabaseName'
2. Connect to your SQL Server 2005 instance and run the following statement:
use master
go
exec sp_attach_db @.dbname='DatabaseName',
@.filename1 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test.mdf',
@.filename2 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test_log.ldf'
Could you please mail me (changliw@.microsoft.com) the SQL error logs and a
screenshot of the error message for further research?
By default, the error logs of SQL Server 2005 instance are located in
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG". You may check it
if there are multiple instances installed on your computer.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
Regards,
Gary Blakely
Try to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>
|||Hi Gary,
SQL Server 2005 Management Studio totally supports attaching SQL Server
2000, MSDE2000 and SQL Express databases by using sp_detach_db/sp_attach_db
stored procedure.
Please try again via the following:
1. Connect to your MSDE instance, and run the following statement:
use master
go
exec sp_detach_db 'YourDatabaseName'
2. Connect to your SQL Server 2005 instance and run the following statement:
use master
go
exec sp_attach_db @.dbname='DatabaseName',
@.filename1 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test.mdf',
@.filename2 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test_log.ldf'
Could you please mail me (changliw@.microsoft.com) the SQL error logs and a
screenshot of the error message for further research?
By default, the error logs of SQL Server 2005 instance are located in
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG". You may check it
if there are multiple instances installed on your computer.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support
Subscribe to:
Posts (Atom)