Showing posts with label home. Show all posts
Showing posts with label home. Show all posts

Wednesday, March 28, 2012

Newbie question about installation

Hi,

I have just downloaded SQL Server 2005 Express Edition and am trying to run the setup. I have Windows XP Home Edition SP2 and I have received an error message saying that my operating system does not meet Service Pack level requirements. The documentation on the website shows that my service pack level is correct. Additionally the message suggests that I install the service pack from http://go.microsoft.com/fwlink/?LinkId=50380 but when I select that I get transferred to another web page which is unrelated.

Any ideas?

Did you install the .NET Framework on the machine (.NET 2.0 with additional fixes) ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

I have seen a couple of people asking this question about the service pack, and it was already loaded on... One of the solutions that has been found is to re run the service pack install on the machine, I would try that.

|||Thanks for the suggestion. I have rerun the download and this time I have had no problem.sql

Monday, March 19, 2012

Newbie Needs Help ;)

Thanks everyone (especially Hilary) for your help.
Apologies for not saying earlier but I left for home for
the weekend (I'm in the UK).
The Replication I set up was from the Microsoft Web page,
can anyone tell me of a guide on 'What to do when things
go wrong ?'
Peter

>--Original Message--
>Hello,
>I'm new to replication. I have got a subscriber,
publisher
>ans distributer working ok, so now does the snapshot
>replication, then the transactional ones.
>It was working fine for 5 minutes then I had the
following
>error
>Cannot update identity column 'ID'.
>{CALL sp_MSupd_tblPerson
>
(NULL,0,NULL,NULL,NULL,NULL,NULL,' ',1,0,7146,0x82
>03)}
>ID is a primary key with an Identity setting get to 'Yes
>but not for replication'.
>Any pointers please
>Peter
>.
>
Peter,
I think the best thing to do is to search this newsgroup. I maintain a short
list of things I have found useful at www.replicationanswers.com which is
not meant to be exhaustive.
There are one or two other articles around that may help:
http://www.microsoft.com/technet/pro.../mergproc.mspx
http://www.databasejournal.com/featu...le.php/1468971
HTH,
Paul Ibison
|||Thanks Paul

>--Original Message--
>Peter,
>I think the best thing to do is to search this newsgroup.
I maintain a short
>list of things I have found useful at
www.replicationanswers.com which is
>not meant to be exhaustive.
>There are one or two other articles around that may help:
>http://www.microsoft.com/technet/pro.../sql/2000/main
tain/mergproc.mspx
>http://www.databasejournal.com/featu...l/article.php/
1468971
>HTH,
>Paul Ibison
>
>.
>

Saturday, February 25, 2012

newbie - empty result set for all queries?

I am a newbie and have installed SQL Server myself on my home machine,
where I'm having problems. When I run the Query Analyzer, I get an
empty result set for all queries, with the message, "The command(s)
completed successfully." So, for instance, if I were to go to
Northwind and type "SELECT * from Employees", which we KNOW isn't
empty, all I see is "The command(s) completed successfully." How do I
get query results?

I thought maybe the problem was permissions. I'm logged into my local
server, which is the computer on which I'm running. The owner is just
"ZIPPY/Owner", ZIPPY being my machine name; since I'm the only one who
uses the computer, I don't even log in, I just take the default "Owner"
account. I start up the SQL analyzer with Windows credentials.

Anyone have a clue what I'm doing wrong?shelah (shelah2@.verizon.net) writes:
> I am a newbie and have installed SQL Server myself on my home machine,
> where I'm having problems. When I run the Query Analyzer, I get an
> empty result set for all queries, with the message, "The command(s)
> completed successfully." So, for instance, if I were to go to
> Northwind and type "SELECT * from Employees", which we KNOW isn't
> empty, all I see is "The command(s) completed successfully." How do I
> get query results?

You are not even getting an empty result set. Apparently you are in some
sort of noexec mode where the query is sent to SQL Server for validation
only.

There are a couple of ways to get this behaviour. First make sure that
you press the green arrow to run the query. The blue tick is for validation
only.

If the problem is not that simple, check Tools->Options->Connection
properties. If any of SET NOEXEC ON or SET PARSEONLY ON are checked,
uncheck them.

If this does not help, send these commands to SQL Server:

SET PARSEONLY OFF
SET NOEXEC OFF
SET FMTONLY OFF

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thank you, that was an enormous help. You were right; I was clicking
the check and not the green arrow. A great relief to know that I have a
usable database and don't have to do some wierd chown gyrations.

*** Sent via Developersdex http://www.developersdex.com ***|||thanks it was a great help even to me
Erland Sommarskog wrote:
> shelah (shelah2@.verizon.net) writes:
> > I am a newbie and have installed SQL Server myself on my home machine,
> > where I'm having problems. When I run the Query Analyzer, I get an
> > empty result set for all queries, with the message, "The command(s)
> > completed successfully." So, for instance, if I were to go to
> > Northwind and type "SELECT * from Employees", which we KNOW isn't
> > empty, all I see is "The command(s) completed successfully." How do I
> > get query results?
> You are not even getting an empty result set. Apparently you are in some
> sort of noexec mode where the query is sent to SQL Server for validation
> only.
> There are a couple of ways to get this behaviour. First make sure that
> you press the green arrow to run the query. The blue tick is for validation
> only.
> If the problem is not that simple, check Tools->Options->Connection
> properties. If any of SET NOEXEC ON or SET PARSEONLY ON are checked,
> uncheck them.
> If this does not help, send these commands to SQL Server:
> SET PARSEONLY OFF
> SET NOEXEC OFF
> SET FMTONLY OFF
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||To avoid this in the future just hit F5

http://sqlservercode.blogspot.com/