I have SQL Server Standard edition (that was installed
after un-installing the Enterprise evaluation copy using
add/remove programs). On Retore screen, the option "Point
in Time' is grayed out totally. How can I make this option
usable?
Thanks.This is a multi-part message in MIME format.
--=_NextPart_000_0375_01C3B80E.61607470
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Your database must be using the Full recovery model - and you must backup
the database as well as the log. Use the STOPAT option when restoring logs.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Neeru" <anonymous@.discussions.microsoft.com> wrote in message
news:019f01c3b837$a98a48b0$a301280a@.phx.gbl...
I have SQL Server Standard edition (that was installed
after un-installing the Enterprise evaluation copy using
add/remove programs). On Retore screen, the option "Point
in Time' is grayed out totally. How can I make this option
usable?
Thanks.
--=_NextPart_000_0375_01C3B80E.61607470
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Your database must be using the Full =recovery model - and you must backup the database as well as the log. Use =the STOPAT option when restoring logs.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Neeru" wrote in message news:019f01c3b837$a9=8a48b0$a301280a@.phx.gbl...I have SQL Server Standard edition (that was installed after =un-installing the Enterprise evaluation copy using add/remove programs). On Retore =screen, the option "Point in Time' is grayed out totally. How can I make this =option usable? Thanks.
--=_NextPart_000_0375_01C3B80E.61607470--|||Thanks, Tom. I used the Maintenace Wizard to create backup
jobs. Is there an option not to use Full Recovery model?
Neeru
>--Original Message--
>Your database must be using the Full recovery model - and
you must backup
>the database as well as the log. Use the STOPAT option
when restoring logs.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Neeru" <anonymous@.discussions.microsoft.com> wrote in
message
>news:019f01c3b837$a98a48b0$a301280a@.phx.gbl...
>I have SQL Server Standard edition (that was installed
>after un-installing the Enterprise evaluation copy using
>add/remove programs). On Retore screen, the option "Point
>in Time' is grayed out totally. How can I make this option
>usable?
>Thanks.
>|||Neeru:
If you want "Point in Time" be enabled then the option "Recovery Model" of
your database must be set to "Full Recovery". To set this option using
Enterprise Manager--> (1) Right Click your database and then click
"Properties" (2) Then click "Options" set and choose "Full" as Recovery
Model.
By this......">> >Your database must be using the Full recovery model -
and you must backup the database as well as the log. >>" Tom meant to
say the same thing but I think you undertood that you are not seeing
"Point-In-Time" because your database is set to "Full Recovery"
"Neeru" <anonymous@.discussions.microsoft.com> wrote in message
news:a85a01c3b83a$629742c0$a601280a@.phx.gbl...
> Thanks, Tom. I used the Maintenace Wizard to create backup
> jobs. Is there an option not to use Full Recovery model?
> Neeru
> >--Original Message--
> >Your database must be using the Full recovery model - and
> you must backup
> >the database as well as the log. Use the STOPAT option
> when restoring logs.
> >
> >--
> >Tom
> >
> >----
> --
> >Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> >SQL Server MVP
> >Columnist, SQL Server Professional
> >Toronto, ON Canada
> >www.pinnaclepublishing.com/sql
> >
> >
> >"Neeru" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:019f01c3b837$a98a48b0$a301280a@.phx.gbl...
> >I have SQL Server Standard edition (that was installed
> >after un-installing the Enterprise evaluation copy using
> >add/remove programs). On Retore screen, the option "Point
> >in Time' is grayed out totally. How can I make this option
> >usable?
> >Thanks.
> >|||THANKS, DON and Tom.
It worked. Have a nice week.
Neeru
>--Original Message--
>Neeru:
>If you want "Point in Time" be enabled then the
option "Recovery Model" of
>your database must be set to "Full Recovery". To set this
option using
>Enterprise Manager--> (1) Right Click your database and
then click
>"Properties" (2) Then click "Options" set and
choose "Full" as Recovery
>Model.
>By this......">> >Your database must be using the Full
recovery model -
>and you must backup the database as well as the log.
>>" Tom meant to
>say the same thing but I think you undertood that you are
not seeing
>"Point-In-Time" because your database is set to "Full
Recovery"
>
>"Neeru" <anonymous@.discussions.microsoft.com> wrote in
message
>news:a85a01c3b83a$629742c0$a601280a@.phx.gbl...
>> Thanks, Tom. I used the Maintenace Wizard to create
backup
>> jobs. Is there an option not to use Full Recovery model?
>> Neeru
>> >--Original Message--
>> >Your database must be using the Full recovery model -
and
>> you must backup
>> >the database as well as the log. Use the STOPAT option
>> when restoring logs.
>> >
>> >--
>> >Tom
>> >
>> >----
--
>> --
>> >Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> >SQL Server MVP
>> >Columnist, SQL Server Professional
>> >Toronto, ON Canada
>> >www.pinnaclepublishing.com/sql
>> >
>> >
>> >"Neeru" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:019f01c3b837$a98a48b0$a301280a@.phx.gbl...
>> >I have SQL Server Standard edition (that was installed
>> >after un-installing the Enterprise evaluation copy
using
>> >add/remove programs). On Retore screen, the
option "Point
>> >in Time' is grayed out totally. How can I make this
option
>> >usable?
>> >Thanks.
>> >
>
>.
>
Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts
Friday, March 23, 2012
Wednesday, March 21, 2012
Plzz help error failed to export crystal report
i ma trying to solve a problem for a couple of days and cannot get around it..I have installed the whole crystal report software on my development machine and have created a report.. and when i try to export it it gaves me failed to export error..if i try like html..it expots but for pdf and rtf it isn't..
on the other side i want to use this report in my vb application..for the time being since the crystal reports install all the files so i dont have to include runtime files for crystsal report to run with vb..i called the report and can export it in html but for pdf and other formats ..even i have enabled the enableexport button..it just doesnt do any thing..how ever when i try to do it manually..by code..pdf export it gives me the same error..failed to export..
i have reinstalled the whole things and this does not work can anyone plzz help meSearch for your solution here
http://support.businessobjects.com/
on the other side i want to use this report in my vb application..for the time being since the crystal reports install all the files so i dont have to include runtime files for crystsal report to run with vb..i called the report and can export it in html but for pdf and other formats ..even i have enabled the enableexport button..it just doesnt do any thing..how ever when i try to do it manually..by code..pdf export it gives me the same error..failed to export..
i have reinstalled the whole things and this does not work can anyone plzz help meSearch for your solution here
http://support.businessobjects.com/
Plz Help!
Hi guys
I have installed SQL 7.0 for the first time and now when I try to
connect in query analyzer I get the following error message:
I have installed SQL 7.0 for the first time and now when I try to
connect in query analyzer I get the following error message:
Unable to connect to server \\localhost:
server:Msg17,level16,state1
[microsoft][odbc sql server driver][dbnet lib]sql server does not exist
or access denied
I have already enabled the TCP/IP
I am using windows XP service pack 2
Thanx a lot in advance for ur kind help
regards
Mr NoviceMrNovice (akhil.gupta04@.gmail.com) writes:
> I have installed SQL 7.0 for the first time and now when I try to
> connect in query analyzer I get the following error message:
> Unable to connect to server \\localhost:
>
> server:Msg17,level16,state1
> [microsoft][odbc sql server driver][dbnet lib]sql server does not exist
> or access denied
>
> I have already enabled the TCP/IP
> I am using windows XP service pack 2
> Thanx a lot in advance for ur kind help
> regards
What did you specify in Query Analyzer for server? "\\localhost"? That's
not a magic name. Try . (a single dot) or "(local)".
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspxsql
Monday, March 12, 2012
PLS HELP! sql exception: SQL Server does not exist or access denied
hI all,
I have sql server 2000 installed on one machine runningwindows server 2003 and using VS 2003 to code and run IIS 5.0 onanother machine running windows XP.
I'm getting the error: sql exception: SQL Server does not exist oraccess denied. But i tried using osql to connect to the sqlserver from the XP machine and it works fine!
Can someone pls help me and tell me why i get this error for my webappbut i can connect to the sql server with osql? Thanks in Advance
bear in mind that the connectionstring is differernt for each machine depends on the machine setting for hte SQL SErver so check that carefully
www.connectionstrings.com
check that and if you have the same problem get back to us with the connection string and error message so we might help
I have sql server 2000 installed on one machine runningwindows server 2003 and using VS 2003 to code and run IIS 5.0 onanother machine running windows XP.
I'm getting the error: sql exception: SQL Server does not exist oraccess denied. But i tried using osql to connect to the sqlserver from the XP machine and it works fine!
Can someone pls help me and tell me why i get this error for my webappbut i can connect to the sql server with osql? Thanks in Advance
bear in mind that the connectionstring is differernt for each machine depends on the machine setting for hte SQL SErver so check that carefully
www.connectionstrings.com
check that and if you have the same problem get back to us with the connection string and error message so we might help
Pls Help - can't install Sql Server Reporting Services
I have Sql Server Personal Edition SP3 installed on my PC. I get an error
message when trying to install the reporting services trial package. Does
the reporting services not work with a personal edition of Sql Server?
The error message is "The edition of the report server database is not
supported on the edition of Sql Server 2000 you have chosen".
Thanks,Paul, I will be interested to see any responses you receive I have been
experiencing the same problems for the past 2 days. With what appear to be
the exact same setup you are running XP SP2, SQL 2000 SP3a and trial edition
of reporting services.
"Paul Tilson" wrote:
> I have Sql Server Personal Edition SP3 installed on my PC. I get an error
> message when trying to install the reporting services trial package. Does
> the reporting services not work with a personal edition of Sql Server?
> The error message is "The edition of the report server database is not
> supported on the edition of Sql Server 2000 you have chosen".
> Thanks,
>
>|||The System Requirements page at
http://www.microsoft.com/sql/reporting/productinfo/sysreqs.asp says that
only Standard, Enterprise, and Developer Editions are supported. If you're
just doing this for trial purposes, how about installing the Evaluation
Edition of SQL Server while you're testing?
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Tilson" <tilsonpa@.yahoo.com> wrote in message
news:10o3egfkodqaic4@.corp.supernews.com...
>I have Sql Server Personal Edition SP3 installed on my PC. I get an error
>message when trying to install the reporting services trial package. Does
>the reporting services not work with a personal edition of Sql Server?
> The error message is "The edition of the report server database is not
> supported on the edition of Sql Server 2000 you have chosen".
> Thanks,
>
message when trying to install the reporting services trial package. Does
the reporting services not work with a personal edition of Sql Server?
The error message is "The edition of the report server database is not
supported on the edition of Sql Server 2000 you have chosen".
Thanks,Paul, I will be interested to see any responses you receive I have been
experiencing the same problems for the past 2 days. With what appear to be
the exact same setup you are running XP SP2, SQL 2000 SP3a and trial edition
of reporting services.
"Paul Tilson" wrote:
> I have Sql Server Personal Edition SP3 installed on my PC. I get an error
> message when trying to install the reporting services trial package. Does
> the reporting services not work with a personal edition of Sql Server?
> The error message is "The edition of the report server database is not
> supported on the edition of Sql Server 2000 you have chosen".
> Thanks,
>
>|||The System Requirements page at
http://www.microsoft.com/sql/reporting/productinfo/sysreqs.asp says that
only Standard, Enterprise, and Developer Editions are supported. If you're
just doing this for trial purposes, how about installing the Evaluation
Edition of SQL Server while you're testing?
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Tilson" <tilsonpa@.yahoo.com> wrote in message
news:10o3egfkodqaic4@.corp.supernews.com...
>I have Sql Server Personal Edition SP3 installed on my PC. I get an error
>message when trying to install the reporting services trial package. Does
>the reporting services not work with a personal edition of Sql Server?
> The error message is "The edition of the report server database is not
> supported on the edition of Sql Server 2000 you have chosen".
> Thanks,
>
Wednesday, March 7, 2012
Please Need Help
Hi all,
I am new to SQL server. I just installed SQL Server express and Visual Web Developer Express edition.
I have experience in SQL but I need some tutorial about how to use SQL Server and create tables and make queries. I can't find any exact location in Microsoft website about SQL Server express documentation where i can find beginner's resources.
Can anyone please give me the location.
Thanks
HI,
You will find a demo on SQL Express at the following link under "Product Resources" that will be a good starting point:
http://www.microsoft.com/sql/editions/express/default.mspx
Also, check out the article "Get Started with SQL Server Express" at http://msdn.microsoft.com/sql/express/
Express documentation is available at http://www.microsoft.com/downloads/details.aspx?familyid=9697aaaa-ad4b-416e-87a4-a8b154f92787&displaylang=en
Thanks,
Sonal
Please Need Help
Hi all,
I am new to SQL server. I just installed SQL Server express and Visual Web Developer Express edition.
I have experience in SQL but I need some tutorial about how to use SQL Server and create tables and make queries. I can't find any exact location in Microsoft website about SQL Server express documentation where i can find beginner's resources.
Can anyone please give me the location.
Thanks
HI,
You will find a demo on SQL Express at the following link under "Product Resources" that will be a good starting point:
http://www.microsoft.com/sql/editions/express/default.mspx
Also, check out the article "Get Started with SQL Server Express" at http://msdn.microsoft.com/sql/express/
Express documentation is available at http://www.microsoft.com/downloads/details.aspx?familyid=9697aaaa-ad4b-416e-87a4-a8b154f92787&displaylang=en
Thanks,
Sonal
Saturday, February 25, 2012
Please help: Can not start Report Server Web Service for 2000
I have spent several days trying to figure it out, I am out of options now.
I have a SQL Server 2000 Standard, patched with SP4, installed on Windows
Server 2003 SP1, I installed Report Server 2000 Standard edition (Report
Server and Report Manager components). At the end of installation, I got a
warning saying that I have to manually initialize Report server for the first
time for it to work. But when I tried somethng like
http://localhost/ReportServer, I received "Service Unavailable". I have made
sure ASP .Net v1.1.4322 is registered with IIS (6.0 SP1), use Network Service
account for ASP .Net, etc. From the event log, itsaid W3Wp encounterd an
application exeption, there was no log for ReportServer.
I really don't know what if going on here as it worked perfectly on another
Windows Server 2003, the difference is that I has Visual Studio .Net 2003
installed on that machine, but I think VS is only necessary if you want to
install Report Designer.
I read through a lot of newsgroup, tried all those suggestions, but still
not be able to fix it.
Thanks in advance for any info.
did you try using RSactivate utility to manually activate report
server?
If yes is it successful, if not what is the error message
|||Yes I did try it, it failed. The message was like " the report server web
service has not generated a public key".
I checked ReportServer database keys table, there is an entry for client =
1, from what I read, it is supposed to have an entry for client = 0 once
http://localhost/ReportServer is invoked or manually activated.
I think the problem is that Report Server web service somehow crashed, that
would explain whay there was no log file like ReportServer_timestamp.txt.
Now I am suspecting it may be because of the patches, Win2003 SP1 or SQL
2000 SP4. The another Win2003 worked has no SP1, and SQL 2000 is SP3.
Unfortunatlly right now rolling back is not an option.
"Shadow" wrote:
> did you try using RSactivate utility to manually activate report
> server?
> If yes is it successful, if not what is the error message
>
I have a SQL Server 2000 Standard, patched with SP4, installed on Windows
Server 2003 SP1, I installed Report Server 2000 Standard edition (Report
Server and Report Manager components). At the end of installation, I got a
warning saying that I have to manually initialize Report server for the first
time for it to work. But when I tried somethng like
http://localhost/ReportServer, I received "Service Unavailable". I have made
sure ASP .Net v1.1.4322 is registered with IIS (6.0 SP1), use Network Service
account for ASP .Net, etc. From the event log, itsaid W3Wp encounterd an
application exeption, there was no log for ReportServer.
I really don't know what if going on here as it worked perfectly on another
Windows Server 2003, the difference is that I has Visual Studio .Net 2003
installed on that machine, but I think VS is only necessary if you want to
install Report Designer.
I read through a lot of newsgroup, tried all those suggestions, but still
not be able to fix it.
Thanks in advance for any info.
did you try using RSactivate utility to manually activate report
server?
If yes is it successful, if not what is the error message
|||Yes I did try it, it failed. The message was like " the report server web
service has not generated a public key".
I checked ReportServer database keys table, there is an entry for client =
1, from what I read, it is supposed to have an entry for client = 0 once
http://localhost/ReportServer is invoked or manually activated.
I think the problem is that Report Server web service somehow crashed, that
would explain whay there was no log file like ReportServer_timestamp.txt.
Now I am suspecting it may be because of the patches, Win2003 SP1 or SQL
2000 SP4. The another Win2003 worked has no SP1, and SQL 2000 is SP3.
Unfortunatlly right now rolling back is not an option.
"Shadow" wrote:
> did you try using RSactivate utility to manually activate report
> server?
> If yes is it successful, if not what is the error message
>
Please help: Can not start Report Server Web Service for 2000
I have spent several days trying to figure it out, I am out of options now.
I have a SQL Server 2000 Standard, patched with SP4, installed on Windows
Server 2003 SP1, I installed Report Server 2000 Standard edition (Report
Server and Report Manager components). At the end of installation, I got a
warning saying that I have to manually initialize Report server for the firs
t
time for it to work. But when I tried somethng like
http://localhost/ReportServer, I received "Service Unavailable". I have made
sure ASP .Net v1.1.4322 is registered with IIS (6.0 SP1), use Network Servic
e
account for ASP .Net, etc. From the event log, itsaid W3Wp encounterd an
application exeption, there was no log for ReportServer.
I really don't know what if going on here as it worked perfectly on another
Windows Server 2003, the difference is that I has Visual Studio .Net 2003
installed on that machine, but I think VS is only necessary if you want to
install Report Designer.
I read through a lot of newsgroup, tried all those suggestions, but still
not be able to fix it.
Thanks in advance for any info.did you try using RSactivate utility to manually activate report
server?
If yes is it successful, if not what is the error message|||Yes I did try it, it failed. The message was like " the report server web
service has not generated a public key".
I checked ReportServer database keys table, there is an entry for client =
1, from what I read, it is supposed to have an entry for client = 0 once
http://localhost/ReportServer is invoked or manually activated.
I think the problem is that Report Server web service somehow crashed, that
would explain whay there was no log file like ReportServer_timestamp.txt.
Now I am suspecting it may be because of the patches, Win2003 SP1 or SQL
2000 SP4. The another Win2003 worked has no SP1, and SQL 2000 is SP3.
Unfortunatlly right now rolling back is not an option.
"Shadow" wrote:
> did you try using RSactivate utility to manually activate report
> server?
> If yes is it successful, if not what is the error message
>
I have a SQL Server 2000 Standard, patched with SP4, installed on Windows
Server 2003 SP1, I installed Report Server 2000 Standard edition (Report
Server and Report Manager components). At the end of installation, I got a
warning saying that I have to manually initialize Report server for the firs
t
time for it to work. But when I tried somethng like
http://localhost/ReportServer, I received "Service Unavailable". I have made
sure ASP .Net v1.1.4322 is registered with IIS (6.0 SP1), use Network Servic
e
account for ASP .Net, etc. From the event log, itsaid W3Wp encounterd an
application exeption, there was no log for ReportServer.
I really don't know what if going on here as it worked perfectly on another
Windows Server 2003, the difference is that I has Visual Studio .Net 2003
installed on that machine, but I think VS is only necessary if you want to
install Report Designer.
I read through a lot of newsgroup, tried all those suggestions, but still
not be able to fix it.
Thanks in advance for any info.did you try using RSactivate utility to manually activate report
server?
If yes is it successful, if not what is the error message|||Yes I did try it, it failed. The message was like " the report server web
service has not generated a public key".
I checked ReportServer database keys table, there is an entry for client =
1, from what I read, it is supposed to have an entry for client = 0 once
http://localhost/ReportServer is invoked or manually activated.
I think the problem is that Report Server web service somehow crashed, that
would explain whay there was no log file like ReportServer_timestamp.txt.
Now I am suspecting it may be because of the patches, Win2003 SP1 or SQL
2000 SP4. The another Win2003 worked has no SP1, and SQL 2000 is SP3.
Unfortunatlly right now rolling back is not an option.
"Shadow" wrote:
> did you try using RSactivate utility to manually activate report
> server?
> If yes is it successful, if not what is the error message
>
Please help: Can not start Report Server Web Service for 2000
I have spent several days trying to figure it out, I am out of options now.
I have a SQL Server 2000 Standard, patched with SP4, installed on Windows
Server 2003 SP1, I installed Report Server 2000 Standard edition (Report
Server and Report Manager components). At the end of installation, I got a
warning saying that I have to manually initialize Report server for the first
time for it to work. But when I tried somethng like
http://localhost/ReportServer, I received "Service Unavailable". I have made
sure ASP .Net v1.1.4322 is registered with IIS (6.0 SP1), use Network Service
account for ASP .Net, etc. From the event log, itsaid W3Wp encounterd an
application exeption, there was no log for ReportServer.
I really don't know what if going on here as it worked perfectly on another
Windows Server 2003, the difference is that I has Visual Studio .Net 2003
installed on that machine, but I think VS is only necessary if you want to
install Report Designer.
I read through a lot of newsgroup, tried all those suggestions, but still
not be able to fix it.
Thanks in advance for any info.did you try using RSactivate utility to manually activate report
server?
If yes is it successful, if not what is the error message|||Yes I did try it, it failed. The message was like " the report server web
service has not generated a public key".
I checked ReportServer database keys table, there is an entry for client =1, from what I read, it is supposed to have an entry for client = 0 once
http://localhost/ReportServer is invoked or manually activated.
I think the problem is that Report Server web service somehow crashed, that
would explain whay there was no log file like ReportServer_timestamp.txt.
Now I am suspecting it may be because of the patches, Win2003 SP1 or SQL
2000 SP4. The another Win2003 worked has no SP1, and SQL 2000 is SP3.
Unfortunatlly right now rolling back is not an option.
"Shadow" wrote:
> did you try using RSactivate utility to manually activate report
> server?
> If yes is it successful, if not what is the error message
>
I have a SQL Server 2000 Standard, patched with SP4, installed on Windows
Server 2003 SP1, I installed Report Server 2000 Standard edition (Report
Server and Report Manager components). At the end of installation, I got a
warning saying that I have to manually initialize Report server for the first
time for it to work. But when I tried somethng like
http://localhost/ReportServer, I received "Service Unavailable". I have made
sure ASP .Net v1.1.4322 is registered with IIS (6.0 SP1), use Network Service
account for ASP .Net, etc. From the event log, itsaid W3Wp encounterd an
application exeption, there was no log for ReportServer.
I really don't know what if going on here as it worked perfectly on another
Windows Server 2003, the difference is that I has Visual Studio .Net 2003
installed on that machine, but I think VS is only necessary if you want to
install Report Designer.
I read through a lot of newsgroup, tried all those suggestions, but still
not be able to fix it.
Thanks in advance for any info.did you try using RSactivate utility to manually activate report
server?
If yes is it successful, if not what is the error message|||Yes I did try it, it failed. The message was like " the report server web
service has not generated a public key".
I checked ReportServer database keys table, there is an entry for client =1, from what I read, it is supposed to have an entry for client = 0 once
http://localhost/ReportServer is invoked or manually activated.
I think the problem is that Report Server web service somehow crashed, that
would explain whay there was no log file like ReportServer_timestamp.txt.
Now I am suspecting it may be because of the patches, Win2003 SP1 or SQL
2000 SP4. The another Win2003 worked has no SP1, and SQL 2000 is SP3.
Unfortunatlly right now rolling back is not an option.
"Shadow" wrote:
> did you try using RSactivate utility to manually activate report
> server?
> If yes is it successful, if not what is the error message
>
Please help.....
We had a NT4 server with SQL 7 installed. AS it happened the machine complete
bombed out. I managed to copy the data folder from the SQL installation
diretory before the whole hdd went up in flames.
I am basically stuck now with *.mdf and *.ldf which both are about 100+ megs
and I really want to import this database into SQL 2000.
I have attached the database succefully and can see it there. Even the OBDC
test is successfull. However the application which is CRM Superoffice doens;t
want to log on as it says invalid username and password.
I am sure that I might have missed seomthing. Do I first need to some
coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind that
we no longer have SQL 7 but just the data directory of that installation. No
backups were done of this machine ( as usual )
Can I do anything at all?
Please, any help is appreciated.
Regards
Gian
Gian
Did you move all logins from source database to the destination?
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
|||Sounds like the database is fine, but you may need to reattach database user
accounts.
See sp_change_users_login to see if you just need to realign the database
user accounts with the logins
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
|||Hi,
Since you did an attach of databases, I am sure that you have not moved the
system databases from sql 7 to sql 2000.
All the SQL server logins will be kept in master database. So since you have
not copied the logins the SID in syslogins will not
match with SID in sysusers of each database. To resync the syslogins with
sysusers, refer the procedure "sp_change_users_login"
in sql server books online.
One more thing is after sync. you may need to make the CRM user to default
to that user database using the below system procedure
sp_defaultdb 'login_name','database_name'
Thanks
Hari
MCDBA
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
|||Gian,
Things to check.
1) Did you import all the logins from the old server?
2) Are the logins mapped to the correct users in your attached database?
sp_change_users_login can help here.
3) Is the security mode the same as the old server? i.e. are you using
Windows Authentication Only or Mixed mode? Check that this is correct
because a standard SQL login will not be allowed on a Windows
Authentication Only server.
Also have a look at:
Microsoft Knowledge Base Article - 224071
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/?id=224071
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gian wrote:
> We had a NT4 server with SQL 7 installed. AS it happened the machine complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+ megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the OBDC
> test is successfull. However the application which is CRM Superoffice doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind that
> we no longer have SQL 7 but just the data directory of that installation. No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
bombed out. I managed to copy the data folder from the SQL installation
diretory before the whole hdd went up in flames.
I am basically stuck now with *.mdf and *.ldf which both are about 100+ megs
and I really want to import this database into SQL 2000.
I have attached the database succefully and can see it there. Even the OBDC
test is successfull. However the application which is CRM Superoffice doens;t
want to log on as it says invalid username and password.
I am sure that I might have missed seomthing. Do I first need to some
coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind that
we no longer have SQL 7 but just the data directory of that installation. No
backups were done of this machine ( as usual )
Can I do anything at all?
Please, any help is appreciated.
Regards
Gian
Gian
Did you move all logins from source database to the destination?
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
|||Sounds like the database is fine, but you may need to reattach database user
accounts.
See sp_change_users_login to see if you just need to realign the database
user accounts with the logins
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
|||Hi,
Since you did an attach of databases, I am sure that you have not moved the
system databases from sql 7 to sql 2000.
All the SQL server logins will be kept in master database. So since you have
not copied the logins the SID in syslogins will not
match with SID in sysusers of each database. To resync the syslogins with
sysusers, refer the procedure "sp_change_users_login"
in sql server books online.
One more thing is after sync. you may need to make the CRM user to default
to that user database using the below system procedure
sp_defaultdb 'login_name','database_name'
Thanks
Hari
MCDBA
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
|||Gian,
Things to check.
1) Did you import all the logins from the old server?
2) Are the logins mapped to the correct users in your attached database?
sp_change_users_login can help here.
3) Is the security mode the same as the old server? i.e. are you using
Windows Authentication Only or Mixed mode? Check that this is correct
because a standard SQL login will not be allowed on a Windows
Authentication Only server.
Also have a look at:
Microsoft Knowledge Base Article - 224071
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/?id=224071
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gian wrote:
> We had a NT4 server with SQL 7 installed. AS it happened the machine complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+ megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the OBDC
> test is successfull. However the application which is CRM Superoffice doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind that
> we no longer have SQL 7 but just the data directory of that installation. No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
Please help.....
We had a NT4 server with SQL 7 installed. AS it happened the machine complete
bombed out. I managed to copy the data folder from the SQL installation
diretory before the whole hdd went up in flames.
I am basically stuck now with *.mdf and *.ldf which both are about 100+ megs
and I really want to import this database into SQL 2000.
I have attached the database succefully and can see it there. Even the OBDC
test is successfull. However the application which is CRM Superoffice doens;t
want to log on as it says invalid username and password.
I am sure that I might have missed seomthing. Do I first need to some
coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind that
we no longer have SQL 7 but just the data directory of that installation. No
backups were done of this machine ( as usual )
Can I do anything at all?
Please, any help is appreciated.
Regards
GianGian
Did you move all logins from source database to the destination?
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian|||Sounds like the database is fine, but you may need to reattach database user
accounts.
See sp_change_users_login to see if you just need to realign the database
user accounts with the logins
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian|||Hi,
Since you did an attach of databases, I am sure that you have not moved the
system databases from sql 7 to sql 2000.
All the SQL server logins will be kept in master database. So since you have
not copied the logins the SID in syslogins will not
match with SID in sysusers of each database. To resync the syslogins with
sysusers, refer the procedure "sp_change_users_login"
in sql server books online.
One more thing is after sync. you may need to make the CRM user to default
to that user database using the below system procedure
sp_defaultdb 'login_name','database_name'
Thanks
Hari
MCDBA
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian|||Gian,
Things to check.
1) Did you import all the logins from the old server?
2) Are the logins mapped to the correct users in your attached database?
sp_change_users_login can help here.
3) Is the security mode the same as the old server? i.e. are you using
Windows Authentication Only or Mixed mode? Check that this is correct
because a standard SQL login will not be allowed on a Windows
Authentication Only server.
Also have a look at:
Microsoft Knowledge Base Article - 224071
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/?id=224071
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gian wrote:
> We had a NT4 server with SQL 7 installed. AS it happened the machine complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+ megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the OBDC
> test is successfull. However the application which is CRM Superoffice doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind that
> we no longer have SQL 7 but just the data directory of that installation. No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
bombed out. I managed to copy the data folder from the SQL installation
diretory before the whole hdd went up in flames.
I am basically stuck now with *.mdf and *.ldf which both are about 100+ megs
and I really want to import this database into SQL 2000.
I have attached the database succefully and can see it there. Even the OBDC
test is successfull. However the application which is CRM Superoffice doens;t
want to log on as it says invalid username and password.
I am sure that I might have missed seomthing. Do I first need to some
coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind that
we no longer have SQL 7 but just the data directory of that installation. No
backups were done of this machine ( as usual )
Can I do anything at all?
Please, any help is appreciated.
Regards
GianGian
Did you move all logins from source database to the destination?
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian|||Sounds like the database is fine, but you may need to reattach database user
accounts.
See sp_change_users_login to see if you just need to realign the database
user accounts with the logins
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian|||Hi,
Since you did an attach of databases, I am sure that you have not moved the
system databases from sql 7 to sql 2000.
All the SQL server logins will be kept in master database. So since you have
not copied the logins the SID in syslogins will not
match with SID in sysusers of each database. To resync the syslogins with
sysusers, refer the procedure "sp_change_users_login"
in sql server books online.
One more thing is after sync. you may need to make the CRM user to default
to that user database using the below system procedure
sp_defaultdb 'login_name','database_name'
Thanks
Hari
MCDBA
"Gian" <Gian@.discussions.microsoft.com> wrote in message
news:E0696A35-26A3-4FAA-BA1C-78E08275F81D@.microsoft.com...
> We had a NT4 server with SQL 7 installed. AS it happened the machine
complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+
megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the
OBDC
> test is successfull. However the application which is CRM Superoffice
doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind
that
> we no longer have SQL 7 but just the data directory of that installation.
No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian|||Gian,
Things to check.
1) Did you import all the logins from the old server?
2) Are the logins mapped to the correct users in your attached database?
sp_change_users_login can help here.
3) Is the security mode the same as the old server? i.e. are you using
Windows Authentication Only or Mixed mode? Check that this is correct
because a standard SQL login will not be allowed on a Windows
Authentication Only server.
Also have a look at:
Microsoft Knowledge Base Article - 224071
Moving SQL Server databases to a new location with Detach/Attach
http://support.microsoft.com/?id=224071
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Gian wrote:
> We had a NT4 server with SQL 7 installed. AS it happened the machine complete
> bombed out. I managed to copy the data folder from the SQL installation
> diretory before the whole hdd went up in flames.
> I am basically stuck now with *.mdf and *.ldf which both are about 100+ megs
> and I really want to import this database into SQL 2000.
> I have attached the database succefully and can see it there. Even the OBDC
> test is successfull. However the application which is CRM Superoffice doens;t
> want to log on as it says invalid username and password.
> I am sure that I might have missed seomthing. Do I first need to some
> coverting of some sort from a SQL 7 to SQl 2000 database? Keep in mind that
> we no longer have SQL 7 but just the data directory of that installation. No
> backups were done of this machine ( as usual )
> Can I do anything at all?
> Please, any help is appreciated.
> Regards
> Gian
Please help.
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-TorontoTry launching your DOS environment and writ 'osql help' at the prompt. That should get u started.
Monday, February 20, 2012
Please Help!!!
I'm running Visual Studio 2005 (VB) with SQL 2005 installed. I tried to add a SQL database and it says SQL express is not installed. And here I was thinking that SQLexpress was only for VS express.
I do not want to use that old crippled handicap SQL express database... how do I use the regular SQL database?
Thanks.
For starters, SQL Express is hardly OLD, it came out at the same time as SQL Server 2005 and is based on the SQL Server 2005 engine. Secondly SQL Express is installed by default with any version of Visual Studio. This doesn't mean you can't have other versions of SQL Server installed on your machine.
Now to answer your question, I think the problem is probably to do with what you are selecting when you attempt to add the database. If you select "Microsoft SqlServer Database File", then VS will attempt to use a Sql Express User Instance which does require SQL Express to be installed, as it is a SQL Express ONLY feature. You need to select the "Microsoft SQL Server" entry, and connect to the appropriate instance of SQL Server.
|||Drae wrote:
I do not want to use that old crippled handicap SQL express database... how do I use the regular SQL database?
Thanks.
It's sad, but I don't think SQLX comes with SQL 2005. Perhaps you can guide me in my moment of darkness...
After creating a project: File| New Project| Windows Application
I select: Project| Add New Item| SQL Database| Add
Error: Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to function properly.
I do not see how I can select SQL 2005 but I would be happy to learn how.
|||
Attaching mdf files is a SQL express only feature called "user instances". A user instance database is for localhost connections only.
You can download SQL express for free.
To connect in a more generic way use View|Server Explorer.
Then click the connect icon. You can connect almost any database.
Karl Tarbet
|||Or just select Tools|Connect To Database and then select Microsoft SQL Server from the list|||
SQLexpress is limited to 4GB, 1CPU, 1GB RAM... which would mean I would have to write code to manage several 4GB DBs and I have a problem with writing code that would have to constantly examine the DB if its nearing 4GB to open a new DB to add records...
Or what happens if you add a record that breaks the 4GB limit... do you crash... and then burn?
|||Drae, if you are at all concerned about reaching the limits placed SQL Express, then you are correct, you should be using a higher SKU of the SQL Server engine. I think it would be counter productive to spend development time attempting to code around the limits of SQL Express, and if you already have appropriately licensed SQL Server to deploy to, then there is no issue.|||Sql express work with vb professional...
Sql server 2005 work with visual studio team....ok?
|||Attaching mdf files is a SQL express only feature called "user instances". A user instance database is for localhost connections only.
So, are you saying that SQL Standard does not have the "user instances" feature; that this feature is only in SQL Express. If so, your reasoning doesn't stand: You can use SQL standard in a localhost connection, so why can't you have a "user instance" with it?
More to the point, someone needs to answer the REAL question: Is it possible to create a database from within Visual Studio using SQL Standard (or higher) (i.e., not Express)?
(In other words, the question is not about creating a connection to a database, but creating the database itself!!)
|||dagilleland, I don't think you quite understand the concept of user instances. Firstly let me state for the record that SQL Server Express or Standard editions will work quite happily and allow you to create and attach to databases from within any version of visual studio 2005. User instances is more about the way in which an end user attaches to the database while using your application. The concept of a user instance implies that an instance of the SQL Server process (sqlservr.exe) is actually spawned off from the parent instance and run under the context of the user that is running the application instead of the service account that would normaly run SQL Server. This feature is ONLY available if you are using SQL Server Express.
For a more detail explaination of user instances and why you might want to use them Roger Wolter wrote a really great article on msdn http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsse/html/sqlexpuserinst.asp
Please Help!!!
I'm running Visual Studio 2005 (VB) with SQL 2005 installed. I tried to add a SQL database and it says SQL express is not installed. And here I was thinking that SQLexpress was only for VS express.
I do not want to use that old crippled handicap SQL express database... how do I use the regular SQL database?
Thanks.
For starters, SQL Express is hardly OLD, it came out at the same time as SQL Server 2005 and is based on the SQL Server 2005 engine. Secondly SQL Express is installed by default with any version of Visual Studio. This doesn't mean you can't have other versions of SQL Server installed on your machine.
Now to answer your question, I think the problem is probably to do with what you are selecting when you attempt to add the database. If you select "Microsoft SqlServer Database File", then VS will attempt to use a Sql Express User Instance which does require SQL Express to be installed, as it is a SQL Express ONLY feature. You need to select the "Microsoft SQL Server" entry, and connect to the appropriate instance of SQL Server.
|||I do not want to use that old crippled handicap SQL express database... how do I use the regular SQL database?
Thanks.
It's sad, but I don't think SQLX comes with SQL 2005. Perhaps you can guide me in my moment of darkness...
After creating a project: File| New Project| Windows Application
I select: Project| Add New Item| SQL Database| Add
Error: Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to function properly.
I do not see how I can select SQL 2005 but I would be happy to learn how.
|||
Attaching mdf files is a SQL express only feature called "user instances". A user instance database is for localhost connections only.
You can download SQL express for free.
To connect in a more generic way use View|Server Explorer.
Then click the connect icon. You can connect almost any database.
Karl Tarbet
|||Or just select Tools|Connect To Database and then select Microsoft SQL Server from the list|||
SQLexpress is limited to 4GB, 1CPU, 1GB RAM... which would mean I would have to write code to manage several 4GB DBs and I have a problem with writing code that would have to constantly examine the DB if its nearing 4GB to open a new DB to add records...
Or what happens if you add a record that breaks the 4GB limit... do you crash... and then burn?
|||Drae, if you are at all concerned about reaching the limits placed SQL Express, then you are correct, you should be using a higher SKU of the SQL Server engine. I think it would be counter productive to spend development time attempting to code around the limits of SQL Express, and if you already have appropriately licensed SQL Server to deploy to, then there is no issue.|||Sql express work with vb professional...
Sql server 2005 work with visual studio team....ok?
|||Attaching mdf files is a SQL express only feature called "user instances". A user instance database is for localhost connections only.
So, are you saying that SQL Standard does not have the "user instances" feature; that this feature is only in SQL Express. If so, your reasoning doesn't stand: You can use SQL standard in a localhost connection, so why can't you have a "user instance" with it?
More to the point, someone needs to answer the REAL question: Is it possible to create a database from within Visual Studio using SQL Standard (or higher) (i.e., not Express)?
(In other words, the question is not about creating a connection to a database, but creating the database itself!!)
|||dagilleland, I don't think you quite understand the concept of user instances. Firstly let me state for the record that SQL Server Express or Standard editions will work quite happily and allow you to create and attach to databases from within any version of visual studio 2005. User instances is more about the way in which an end user attaches to the database while using your application. The concept of a user instance implies that an instance of the SQL Server process (sqlservr.exe) is actually spawned off from the parent instance and run under the context of the user that is running the application instead of the service account that would normaly run SQL Server. This feature is ONLY available if you are using SQL Server Express.
For a more detail explaination of user instances and why you might want to use them Roger Wolter wrote a really great article on msdn http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsse/html/sqlexpuserinst.asp
Please Help! Service Pack update Cannot Verify User with SA login
I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
Services & Manager,Decision Service Objects and Client Components. Afterwards
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?
Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwards
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says it
> could not verify user even though I have even changed the password and know
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?
Services & Manager,Decision Service Objects and Client Components. Afterwards
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?
Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwards
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says it
> could not verify user even though I have even changed the password and know
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?
Please Help! Service Pack update Cannot Verify User with SA login
I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
Services & Manager,Decision Service Objects and Client Components. Afterward
s
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwa
rds
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says i
t
> could not verify user even though I have even changed the password and kno
w
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?
Services & Manager,Decision Service Objects and Client Components. Afterward
s
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwa
rds
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says i
t
> could not verify user even though I have even changed the password and kno
w
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?
Please Help! Service Pack update Cannot Verify User with SA login
I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
Services & Manager,Decision Service Objects and Client Components. Afterwards
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwards
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says it
> could not verify user even though I have even changed the password and know
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?
Services & Manager,Decision Service Objects and Client Components. Afterwards
I tried to run the update that MS put out for Analysis Services and in the
install you have two options: Use user logged on authentication or use SQL
authentication and provide the SA password. I do this and it always says it
could not verify user even though I have even changed the password and know
that it is correct. I am running SQL in Mixed Mode Authentication if this
makes a difference?Also, Service Pack 3 was already installed on this server for SQL, But
Analysis Services and Manager was not. So I installed them. So Do I still
need to run the update. There are 3 different files for updateing SQL. 1.
Database Components
2. Analysis Services
3. Desktop Engine
But I get the error that I mentioned when I run the analysis update!
"Jay" wrote:
> I have SQL 2000 that has Service Pack 3 installed. So I installed Analysis
> Services & Manager,Decision Service Objects and Client Components. Afterwards
> I tried to run the update that MS put out for Analysis Services and in the
> install you have two options: Use user logged on authentication or use SQL
> authentication and provide the SA password. I do this and it always says it
> could not verify user even though I have even changed the password and know
> that it is correct. I am running SQL in Mixed Mode Authentication if this
> makes a difference?
Subscribe to:
Posts (Atom)