Flood of SQL services

Hi,

I've just setup SQL Express 2005 SP2 on my fresh SBS 2003 R2 system. I never had anything to do with and have no idea about SQL, the only reason for updating from MSDE was the annoying and ugly event id 1000 relating to sharepoint services in my application log. There seems to be no working solution for that yet.

The point after upgrading to 2005 SP2 now is, that there is a total of seven services related to SQL running on my machine. They are named

MSSQL$SBSMONITORING

MSSQL$SHAREPOINT

SQL Server (SQLEXPRESS)

SQL Server VSS Writer

SQL Server-Browser

SQLAgent$SBSMONITORING

SQLAgent$Sharepoint

Especially the duplicate services regarding SBS-Monitoring and Sharepoint Services are eye-catchers to me. I thought updating to Express 2005 would trail existing databases - or at least asks you whether to do. And in control panel / software there are still two entries relating to MSDE as well.

Is that all alright? Could an SQL-MVP like me, who has no idea about SQL and hates software cadavers on his system, remove "old" MSDE without crashing the whole system?

Thanks in advance for a hint.

Regards,

Tim

By the way: at least after first reboot of the server there is everything "blue" in application log! :-))

hi,

you have to "uncheck" the "hide advanced configuration options" in the wizard as, by default, the setup package installs a named instance named "SQLExpress" as you can see from you "situation" as well..

if you uncheck that option, you can then specify the instance name and, in your case, you will select the already installed instance.. this will upgrade that instance to SQLExpress edition and not install a new one.. so, in the "Instance name" installation step, press the "Installed instances" button and all local installed instance will be listed... select the MSDE instance you like to upgrade and proceed..

in your scenario, you can eventually maintain the .\SQLExpress installed named instance and just uninstall the MSDE instance..

regards

Flood of SQL services

Hi,
I've just setup SQL Express 2005 SP2 on my fresh SBS 2003 R2 system. I never
had anything to do with and have no idea about SQL, the only reason for
updating from MSDE was the annoying and ugly event id 1000 relating to
sharepoint services in my application log. There seems to be no working
solution for that yet.
The point after upgrading to 2005 SP2 now is, that there is a total of seven
services related to SQL running on my machine. They are named
MSSQL$SBSMONITORING
MSSQL$SHAREPOINT
SQL Server (SQLEXPRESS)
SQL Server VSS Writer
SQL Server-Browser
SQLAgent$SBSMONITORING
SQLAgent$Sharepoint
Especially the duplicate services regarding SBS-Monitoring and Sharepoint
Services are eye-catchers to me. I thought updating to Express 2005 would
trail existing databases - or at least asks you whether to do. And in control
panel / software there are still two entries relating to MSDE as well.
Is that all alright? Could an SQL-MVP like me, who has no idea about SQL and
hates software cadavers on his system, remove "old" MSDE without crashing the
whole system?
Thanks in advance for a hint.
Regards,
Tim
By the way: at least after first reboot of the server there is everything
"blue" in application log! :-))
SQL Agent is essentially a part of SQL Server. It manages scheduled jobs,
alerts, etc. It cannot be removed from the corresponding SQL Server
instance. According to what I see, you have essentially 3 instances of SQL
Server running on your machine, one of which is SQL Express.
BTW, when did you become an MVP? I don't see you listed.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Tim Meltzer" <TimMeltzer@.discussions.microsoft.com> wrote in message
news:C2C0D24F-1B83-43D3-B3FA-95C951907BAC@.microsoft.com...
Hi,
I've just setup SQL Express 2005 SP2 on my fresh SBS 2003 R2 system. I never
had anything to do with and have no idea about SQL, the only reason for
updating from MSDE was the annoying and ugly event id 1000 relating to
sharepoint services in my application log. There seems to be no working
solution for that yet.
The point after upgrading to 2005 SP2 now is, that there is a total of seven
services related to SQL running on my machine. They are named
MSSQL$SBSMONITORING
MSSQL$SHAREPOINT
SQL Server (SQLEXPRESS)
SQL Server VSS Writer
SQL Server-Browser
SQLAgent$SBSMONITORING
SQLAgent$Sharepoint
Especially the duplicate services regarding SBS-Monitoring and Sharepoint
Services are eye-catchers to me. I thought updating to Express 2005 would
trail existing databases - or at least asks you whether to do. And in
control
panel / software there are still two entries relating to MSDE as well.
Is that all alright? Could an SQL-MVP like me, who has no idea about SQL and
hates software cadavers on his system, remove "old" MSDE without crashing
the
whole system?
Thanks in advance for a hint.
Regards,
Tim
By the way: at least after first reboot of the server there is everything
"blue" in application log! :-))
sql

Flood of SQL services

Hi,
I've just setup SQL Express 2005 SP2 on my fresh SBS 2003 R2 system. I never
had anything to do with and have no idea about SQL, the only reason for
updating from MSDE was the annoying and ugly event id 1000 relating to
sharepoint services in my application log. There seems to be no working
solution for that yet.
The point after upgrading to 2005 SP2 now is, that there is a total of seven
services related to SQL running on my machine. They are named
MSSQL$SBSMONITORING
MSSQL$SHAREPOINT
SQL Server (SQLEXPRESS)
SQL Server VSS Writer
SQL Server-Browser
SQLAgent$SBSMONITORING
SQLAgent$Sharepoint
Especially the duplicate services regarding SBS-Monitoring and Sharepoint
Services are eye-catchers to me. I thought updating to Express 2005 would
trail existing databases - or at least asks you whether to do. And in contro
l
panel / software there are still two entries relating to MSDE as well.
Is that all alright? Could an SQL-MVP like me, who has no idea about SQL and
hates software cadavers on his system, remove "old" MSDE without crashing th
e
whole system?
Thanks in advance for a hint.
Regards,
Tim
By the way: at least after first reboot of the server there is everything
"blue" in application log! :-))SQL Agent is essentially a part of SQL Server. It manages scheduled jobs,
alerts, etc. It cannot be removed from the corresponding SQL Server
instance. According to what I see, you have essentially 3 instances of SQL
Server running on your machine, one of which is SQL Express.
BTW, when did you become an MVP? I don't see you listed.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Tim Meltzer" <TimMeltzer@.discussions.microsoft.com> wrote in message
news:C2C0D24F-1B83-43D3-B3FA-95C951907BAC@.microsoft.com...
Hi,
I've just setup SQL Express 2005 SP2 on my fresh SBS 2003 R2 system. I never
had anything to do with and have no idea about SQL, the only reason for
updating from MSDE was the annoying and ugly event id 1000 relating to
sharepoint services in my application log. There seems to be no working
solution for that yet.
The point after upgrading to 2005 SP2 now is, that there is a total of seven
services related to SQL running on my machine. They are named
MSSQL$SBSMONITORING
MSSQL$SHAREPOINT
SQL Server (SQLEXPRESS)
SQL Server VSS Writer
SQL Server-Browser
SQLAgent$SBSMONITORING
SQLAgent$Sharepoint
Especially the duplicate services regarding SBS-Monitoring and Sharepoint
Services are eye-catchers to me. I thought updating to Express 2005 would
trail existing databases - or at least asks you whether to do. And in
control
panel / software there are still two entries relating to MSDE as well.
Is that all alright? Could an SQL-MVP like me, who has no idea about SQL and
hates software cadavers on his system, remove "old" MSDE without crashing
the
whole system?
Thanks in advance for a hint.
Regards,
Tim
By the way: at least after first reboot of the server there is everything
"blue" in application log! :-))

Flood of SQL services

Hi,
I've just setup SQL Express 2005 SP2 on my fresh SBS 2003 R2 system. I never
had anything to do with and have no idea about SQL, the only reason for
updating from MSDE was the annoying and ugly event id 1000 relating to
sharepoint services in my application log. There seems to be no working
solution for that yet.
The point after upgrading to 2005 SP2 now is, that there is a total of seven
services related to SQL running on my machine. They are named
MSSQL$SBSMONITORING
MSSQL$SHAREPOINT
SQL Server (SQLEXPRESS)
SQL Server VSS Writer
SQL Server-Browser
SQLAgent$SBSMONITORING
SQLAgent$Sharepoint
Especially the duplicate services regarding SBS-Monitoring and Sharepoint
Services are eye-catchers to me. I thought updating to Express 2005 would
trail existing databases - or at least asks you whether to do. And in control
panel / software there are still two entries relating to MSDE as well.
Is that all alright? Could an SQL-MVP like me, who has no idea about SQL and
hates software cadavers on his system, remove "old" MSDE without crashing the
whole system?
Thanks in advance for a hint.
Regards,
Tim
By the way: at least after first reboot of the server there is everything
"blue" in application log! :-))SQL Agent is essentially a part of SQL Server. It manages scheduled jobs,
alerts, etc. It cannot be removed from the corresponding SQL Server
instance. According to what I see, you have essentially 3 instances of SQL
Server running on your machine, one of which is SQL Express.
BTW, when did you become an MVP? I don't see you listed.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Tim Meltzer" <TimMeltzer@.discussions.microsoft.com> wrote in message
news:C2C0D24F-1B83-43D3-B3FA-95C951907BAC@.microsoft.com...
Hi,
I've just setup SQL Express 2005 SP2 on my fresh SBS 2003 R2 system. I never
had anything to do with and have no idea about SQL, the only reason for
updating from MSDE was the annoying and ugly event id 1000 relating to
sharepoint services in my application log. There seems to be no working
solution for that yet.
The point after upgrading to 2005 SP2 now is, that there is a total of seven
services related to SQL running on my machine. They are named
MSSQL$SBSMONITORING
MSSQL$SHAREPOINT
SQL Server (SQLEXPRESS)
SQL Server VSS Writer
SQL Server-Browser
SQLAgent$SBSMONITORING
SQLAgent$Sharepoint
Especially the duplicate services regarding SBS-Monitoring and Sharepoint
Services are eye-catchers to me. I thought updating to Express 2005 would
trail existing databases - or at least asks you whether to do. And in
control
panel / software there are still two entries relating to MSDE as well.
Is that all alright? Could an SQL-MVP like me, who has no idea about SQL and
hates software cadavers on his system, remove "old" MSDE without crashing
the
whole system?
Thanks in advance for a hint.
Regards,
Tim
By the way: at least after first reboot of the server there is everything
"blue" in application log! :-))

Flat file source component hangs after installing SP2

Hi there,

after we've upgraded to SP2 my flat-file-source component hangs in the validation phase.

normally at 50% or 66%.

i see no activity what-so-ever cpu-wise/memory-wise.

have no idea how to fix it.

(sorry if i am posting this twice, couldn't see my previous post)

Hi Mafti,

could you give us more information about your flat file source configuration? What type of flat file, how many columns, etc?

Also, could you make sure it actually hangs in the flat file source: copy your package and simplify it to have only a single data flow with the single flat file source connected to the row count?

Thanks.

FKs don't publish?

I am using SQL2005 SP2 and noticed that the foreign keys don't publish
to the subscribers. Is this normal?
Thanks,
Peter Cwik
Peter,
It depends. Does this help?
http://technet.microsoft.com/en-us/library/ms180843.aspx
RLF
"PeterCwik" <pjcwik@.gmail.com> wrote in message
news:da63593c-961a-49e6-a511-96d7d60130ec@.k8g2000hsf.googlegroups.com...
>I am using SQL2005 SP2 and noticed that the foreign keys don't publish
> to the subscribers. Is this normal?
> Thanks,
> Peter Cwik
|||On Jan 3, 9:09Xam, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Peter,
> It depends. XDoes this help?http://technet.microsoft.com/en-us/library/ms180843.aspx
> RLF
> "PeterCwik" <pjc...@.gmail.com> wrote in message
> news:da63593c-961a-49e6-a511-96d7d60130ec@.k8g2000hsf.googlegroups.com...
>
>
> - Show quoted text -
Unfortunately, no. The foreign key is set to Yes for Enforce For
Replication.
|||you need to look at the article properties. There is an option to copy
foreign key constraints - make sure this is set to true.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"PeterCwik" <pjcwik@.gmail.com> wrote in message
news:da63593c-961a-49e6-a511-96d7d60130ec@.k8g2000hsf.googlegroups.com...
>I am using SQL2005 SP2 and noticed that the foreign keys don't publish
> to the subscribers. Is this normal?
> Thanks,
> Peter Cwik

Fit-to-page printing

How can I print reports to be fit-to-page. I have SP2 installed.
Are there any scripting or external assembly solutions ?
--
KolithaI have the same problem. I haven't installed SP yet...
Does anyone know how to do that?
Thanks
Chieko
"Kolitha de Silva" wrote:
> How can I print reports to be fit-to-page. I have SP2 installed.
> Are there any scripting or external assembly solutions ?
> --
> Kolitha

Firewall Setting for XP Professional

We have installed SQL Server Evaluation copy on a Windows
XP Professional Workstation with SP2 installed. We also
installed Reporting Services on that workstation as well.
We would like to access the reports on that workstation
from a remote workstation. In this way, we would like to
know what is the best way to open the firewall ? Is it
only for us to add C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\sqlservr.exe in the exception list ?
ThanksHi
http://support.microsoft.com/?kbid=841249
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel" wrote:
> We have installed SQL Server Evaluation copy on a Windows
> XP Professional Workstation with SP2 installed. We also
> installed Reporting Services on that workstation as well.
> We would like to access the reports on that workstation
> from a remote workstation. In this way, we would like to
> know what is the best way to open the firewall ? Is it
> only for us to add C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\sqlservr.exe in the exception list ?
> Thanks
>
>

Firewall Setting for XP Professional

We have installed SQL Server Evaluation copy on a Windows
XP Professional Workstation with SP2 installed. We also
installed Reporting Services on that workstation as well.
We would like to access the reports on that workstation
from a remote workstation. In this way, we would like to
know what is the best way to open the firewall ? Is it
only for us to add C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\sqlservr.exe in the exception list ?
Thanks
Hi
http://support.microsoft.com/?kbid=841249
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel" wrote:

> We have installed SQL Server Evaluation copy on a Windows
> XP Professional Workstation with SP2 installed. We also
> installed Reporting Services on that workstation as well.
> We would like to access the reports on that workstation
> from a remote workstation. In this way, we would like to
> know what is the best way to open the firewall ? Is it
> only for us to add C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\sqlservr.exe in the exception list ?
> Thanks
>
>

Firewall Setting for XP Professional

We have installed SQL Server Evaluation copy on a Windows
XP Professional Workstation with SP2 installed. We also
installed Reporting Services on that workstation as well.
We would like to access the reports on that workstation
from a remote workstation. In this way, we would like to
know what is the best way to open the firewall ? Is it
only for us to add C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\sqlservr.exe in the exception list ?
ThanksHi
http://support.microsoft.com/?kbid=841249
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Daniel" wrote:

> We have installed SQL Server Evaluation copy on a Windows
> XP Professional Workstation with SP2 installed. We also
> installed Reporting Services on that workstation as well.
> We would like to access the reports on that workstation
> from a remote workstation. In this way, we would like to
> know what is the best way to open the firewall ? Is it
> only for us to add C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\sqlservr.exe in the exception list ?
> Thanks
>
>