Mobile Only? Why?

I've just finished installing the workstation tools from the SQL Server 2005
DVD (No database engine).
I've also installed Visual Studio 2005, with just the VB option and the
other standard stuff.
When I start the Management Studio, connect to a server (doesn't matter what
version), then open a new query, the query is disconnected and the only
connection option is for SQL Server Mobile.
Anyone have any ideas?
I've installed (and repaired) the native client. I can browse servers and
see objects, etc., just no queries. I've installed/uninstalled three times.
Thanks all.
Am I correct that you are talking about the New Query dialog box in
Management Studio? On the File menu, point to New, do you see Database
Engine Query as one of the choices?
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:u3yzF5H7FHA.1020@.TK2MSFTNGP15.phx.gbl...
> I've just finished installing the workstation tools from the SQL Server
> 2005 DVD (No database engine).
> I've also installed Visual Studio 2005, with just the VB option and the
> other standard stuff.
> When I start the Management Studio, connect to a server (doesn't matter
> what version), then open a new query, the query is disconnected and the
> only connection option is for SQL Server Mobile.
> Anyone have any ideas?
> I've installed (and repaired) the native client. I can browse servers and
> see objects, etc., just no queries. I've installed/uninstalled three
> times.
> Thanks all.
>
|||Yes, the dropdown (to select a provider) is disabled with SQL Server Mobile
being the selected item.
"Rick Byham [MS]" <rickbyh@.online.microsoft.com> wrote in message
news:%23WgVl5s7FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Am I correct that you are talking about the New Query dialog box in
> Management Studio? On the File menu, point to New, do you see Database
> Engine Query as one of the choices?
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Lead Technical Writer,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "David Pendleton" <qnircra@.gpd.arg> wrote in message
> news:u3yzF5H7FHA.1020@.TK2MSFTNGP15.phx.gbl...
>
|||I've shopped your e-mail around Microsoft a bit, and we can't think of any
reasonable way you could get into that condition. The obvious but cop-out
answer is that either Management Studio or the underlying Visual Studio is
somehow damaged. It's less likely to be related to the SQL Native Client.
Some more questions:
Are you using the RTM version of SQL Server Management Studio?
How consistent is this problem? That is, there are several ways to open the
Connect to Server dialog box in Management Studio:
- On the File menu, point to New, and then click Database Engine Query
- On the Standard toolbar, click New Query
- On the Standard toolbar, click Database Engine Query
- On the Object Explorer toolbar, click Connect, and then click Database
Engine
Do you only get SQL Server Mobile with any of those ways?
What about registering servers? On the View menu click Register Servers. In
the Registered Servers window toolbar, click Database Engine. Now can you
register a Database Engine by right-clicking Database Engine, point to New,
and then click Server Registration? Now is the Server type listed as
"Database Engine"?
Can you connect to the Database Engine from the Server Explorer of Visual
Studio?
(I'm interested in assisting you but I will not be available again until
Monday. Sorry. Holiday plans.)
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:%235DXeAt7FHA.2816@.tk2msftngp13.phx.gbl...
> Yes, the dropdown (to select a provider) is disabled with SQL Server
> Mobile being the selected item.
>
> "Rick Byham [MS]" <rickbyh@.online.microsoft.com> wrote in message
> news:%23WgVl5s7FHA.1420@.TK2MSFTNGP09.phx.gbl...
>
|||Yes, I'm using the version handed out in Vegas at the launch.
I have tried all the connection methods detailed below with the same
results. I am able to register, and connect to a database server and browse
objects, etc.
"Rick Byham [MS]" <rickbyh@.online.microsoft.com> wrote in message
news:%23Ukue367FHA.1416@.TK2MSFTNGP09.phx.gbl...
> I've shopped your e-mail around Microsoft a bit, and we can't think of any
> reasonable way you could get into that condition. The obvious but cop-out
> answer is that either Management Studio or the underlying Visual Studio is
> somehow damaged. It's less likely to be related to the SQL Native Client.
> Some more questions:
> Are you using the RTM version of SQL Server Management Studio?
> How consistent is this problem? That is, there are several ways to open
> the Connect to Server dialog box in Management Studio:
> - On the File menu, point to New, and then click Database Engine Query
> - On the Standard toolbar, click New Query
> - On the Standard toolbar, click Database Engine Query
> - On the Object Explorer toolbar, click Connect, and then click Database
> Engine
> Do you only get SQL Server Mobile with any of those ways?
> What about registering servers? On the View menu click Register Servers.
> In the Registered Servers window toolbar, click Database Engine. Now can
> you register a Database Engine by right-clicking Database Engine, point to
> New, and then click Server Registration? Now is the Server type listed as
> "Database Engine"?
> Can you connect to the Database Engine from the Server Explorer of Visual
> Studio?
> (I'm interested in assisting you but I will not be available again until
> Monday. Sorry. Holiday plans.)
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Lead Technical Writer,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "David Pendleton" <qnircra@.gpd.arg> wrote in message
> news:%235DXeAt7FHA.2816@.tk2msftngp13.phx.gbl...
>
|||If you can browse objects, I presume that means you can connect with Object
Explorer. What happens in Object Explorer if you right-click a database, and
then click New Query? You should get a Database Engine query window. Does
that work? This will tell us if the Query Editor is working properly.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:OVXgegF9FHA.808@.TK2MSFTNGP09.phx.gbl...
> Yes, I'm using the version handed out in Vegas at the launch.
> I have tried all the connection methods detailed below with the same
> results. I am able to register, and connect to a database server and
> browse objects, etc.
>
> "Rick Byham [MS]" <rickbyh@.online.microsoft.com> wrote in message
> news:%23Ukue367FHA.1416@.TK2MSFTNGP09.phx.gbl...
>
|||It comes up as a disconnected query. When I right-click in the query window
and select connect, the connection dialog appears.
In this dialog, the dropdown (to select a provider) is disabled and SQL
Server Mobile is the selected item.
Thanks.
"Rick Byham [MS]" <rickbyh@.online.microsoft.com> wrote in message
news:O5X4uld9FHA.3360@.TK2MSFTNGP11.phx.gbl...
> If you can browse objects, I presume that means you can connect with
> Object Explorer. What happens in Object Explorer if you right-click a
> database, and then click New Query? You should get a Database Engine query
> window. Does that work? This will tell us if the Query Editor is working
> properly.
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Lead Technical Writer,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "David Pendleton" <qnircra@.gpd.arg> wrote in message
> news:OVXgegF9FHA.808@.TK2MSFTNGP09.phx.gbl...
>
|||I sorry. I know this must be frustrating for you, but I can think of no
reason for this. Since you have already uninstalled and reinstalled that
should have fixed any damaged binaries or registry entries. I'm out of
ideas. I guess that means you need a call to product support.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"David Pendleton" <qnircra@.gpd.arg> wrote in message
news:OYVPHzo9FHA.500@.TK2MSFTNGP15.phx.gbl...
> It comes up as a disconnected query. When I right-click in the query
> window and select connect, the connection dialog appears.
> In this dialog, the dropdown (to select a provider) is disabled and SQL
> Server Mobile is the selected item.
> Thanks.
> "Rick Byham [MS]" <rickbyh@.online.microsoft.com> wrote in message
> news:O5X4uld9FHA.3360@.TK2MSFTNGP11.phx.gbl...
>
|||Thanks for trying, anyway.
I'm out of ideas, also. I have successfully installed it on a second
workstation and laptop, both more or less identically configured.
It's probably about time I rebuilt this one anyway, it's been five years...
Thanks again.
Dave
"Rick Byham [MS]" <rickbyh@.online.microsoft.com> wrote in message
news:eyd$Pyp9FHA.952@.TK2MSFTNGP12.phx.gbl...
>I sorry. I know this must be frustrating for you, but I can think of no
>reason for this. Since you have already uninstalled and reinstalled that
>should have fixed any damaged binaries or registry entries. I'm out of
>ideas. I guess that means you need a call to product support.
> --
> Rick Byham
> MCDBA, MCSE, MCSA
> Lead Technical Writer,
> Microsoft, SQL Server Books Online
> This posting is provided "as is" with
> no warranties, and confers no rights.
> "David Pendleton" <qnircra@.gpd.arg> wrote in message
> news:OYVPHzo9FHA.500@.TK2MSFTNGP15.phx.gbl...
>
sql

mmc.exe-Entry point not found in Enterprise Manager

I recently installed SQL 2000 on my machine and it was running fine till I i
nstalled SQL7 on the same machine. Now the SQL7 is running okay but I can't
use SQL2000 anymore. I received the following while try to open Enterprise
Manager:
mmc-entry point not found
The procedure entry point ? loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PB
G@.Z could
not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ? loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PB
G@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.|||Thank you guys. I will give it a try.

mmc.exe-Entry point not found in Enterprise Manager

I recently installed SQL 2000 on my machine and it was running fine till I installed SQL7 on the same machine. Now the SQL7 is running okay but I can't use SQL2000 anymore. I received the following while try to open Enterprise Manager:
mmc-entry point not found
The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.
Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.
|||Thank you guys. I will give it a try.

mmc.exe-Entry point not found in Enterprise Manager

I recently installed SQL 2000 on my machine and it was running fine till I installed SQL7 on the same machine. Now the SQL7 is running okay but I can't use SQL2000 anymore. I received the following while try to open Enterprise Manager
mmc-entry point not foun
The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be located in the dynamic link library SEMCOMN.dll
Can anyone provide me with some advise? Thanks in advance.Uninstall SQL Server 7.0 and 2000. If you still have to
use SQL Server 7.0 First, Install SQL Server 7.0 as the
default then, Install SQL Server 2000 as the named
instance.
>--Original Message--
>I recently installed SQL 2000 on my machine and it was
running fine till I installed SQL7 on the same machine.
Now the SQL7 is running okay but I can't use SQL2000
anymore. I received the following while try to open
Enterprise Manager:
>mmc-entry point not found
>The procedure entry point ?
loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z could not be
located in the dynamic link library SEMCOMN.dll
>Can anyone provide me with some advise? Thanks in
advance.
>.
>|||Ling,
I agree with Tom.Though not officially stated(or is it?), its a good
practice to install SQL7 first and then proceed with the SQL2000 one.In your
case, instead of trying to play around with (un)registering the dlls, go
ahead and uninstall SQL7.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Ling" <anonymous@.discussions.microsoft.com> wrote in message
news:CDFD0161-D3A2-4717-88BD-52ADF1C56322@.microsoft.com...
> I recently installed SQL 2000 on my machine and it was running fine till I
installed SQL7 on the same machine. Now the SQL7 is running okay but I
can't use SQL2000 anymore. I received the following while try to open
Enterprise Manager:
> mmc-entry point not found
> The procedure entry point ?loadSQLToolsLibrary@.@.YAPAUHINSTANCE_@.@.PBG@.Z
could not be located in the dynamic link library SEMCOMN.dll
> Can anyone provide me with some advise? Thanks in advance.|||Thank you guys. I will give it a try.sql

mixing SQL2K and SQL2K5

Has anyone had two instances with these two versions installed in Production
yet? Any gotchas? Any compelling reasons to not do this?
--
TIA,
ChrisRHi
Biggest issue would be that you can't restore the SQL Server 2005 database
in SQL Server 2000.
Otherwise, as long as you test your application that it works on SQL Server
2005, no issues.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1ED99E08-D747-4E13-BB7B-005A742FD458@.microsoft.com...
> Has anyone had two instances with these two versions installed in
> Production
> yet? Any gotchas? Any compelling reasons to not do this?
> --
> TIA,
> ChrisR

mixing SQL2K and SQL2K5

Has anyone had two instances with these two versions installed in Production
yet? Any gotchas? Any compelling reasons to not do this?
TIA,
ChrisR
Hi
Biggest issue would be that you can't restore the SQL Server 2005 database
in SQL Server 2000.
Otherwise, as long as you test your application that it works on SQL Server
2005, no issues.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1ED99E08-D747-4E13-BB7B-005A742FD458@.microsoft.com...
> Has anyone had two instances with these two versions installed in
> Production
> yet? Any gotchas? Any compelling reasons to not do this?
> --
> TIA,
> ChrisR

mixing SQL2K and SQL2K5

Has anyone had two instances with these two versions installed in Production
yet? Any gotchas? Any compelling reasons to not do this?
TIA,
ChrisRHi
Biggest issue would be that you can't restore the SQL Server 2005 database
in SQL Server 2000.
Otherwise, as long as you test your application that it works on SQL Server
2005, no issues.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1ED99E08-D747-4E13-BB7B-005A742FD458@.microsoft.com...
> Has anyone had two instances with these two versions installed in
> Production
> yet? Any gotchas? Any compelling reasons to not do this?
> --
> TIA,
> ChrisR

Missing What To Start SQLServer Agent in EM

Installed Office service pack and it 'messed' up the Enterprise Manager. Af
ter reinstalling the client tools and the sp3a service pack all worked but s
cheduled jobs. It turns out that the SQL Server Agent is not running. It d
oesn't automatically start
up but can be started from DOS whereby my jobs in turn can execute with no p
roblem.
Would like to know what the proper registry setting for SQLServerAgent under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLServerAgent should
be for SQL Server 8.0.859 with service pack 3a as suspect that the problem m
ay be there.
Otherwise open to suggestions so that do not have to backup, uninstall, and
reinstall 10 database.....
Thanxs,
dmatta59The first thing to do here is go into the Control Panel -> Admin Tools ->
Services applet & see if the SQLAgent$[instance] service is configured t
o
auto-start. Your post doesn't indicated that you've done that, so make sure
the service's "Startup Type" property is set to "Automatic". If it still
doesn't start automatically, check the Windows Event Log to see what's
wrong.
Regards,
Greg Linwood
SQL Server MVP
"dmatta59" <anonymous@.discussions.microsoft.com> wrote in message
news:6F7A83AF-FE7A-46EF-8F44-50C94788109C@.microsoft.com...
> Installed Office service pack and it 'messed' up the Enterprise Manager.
After reinstalling the client tools and the sp3a service pack all worked but
scheduled jobs. It turns out that the SQL Server Agent is not running. It
doesn't automatically start up but can be started from DOS whereby my jobs
in turn can execute with no problem.
> Would like to know what the proper registry setting for SQLServerAgent
under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLServerAgent
should be for SQL Server 8.0.859 with service pack 3a as suspect that the
problem may be there.
> Otherwise open to suggestions so that do not have to backup, uninstall,
and reinstall 10 database.....
> Thanxs,
> dmatta59|||The SqlServerAgent is set to automatic. There used to be an error 8344 Supe
rSocket Error but after the registers were cleaned and errors removed the e
rror no longer appears. When viewing the registry for SQLServerAgent there
was some mention in one of
the previous posts about a "dependancies" which is not present so would app
reciate what the registry would look like for MSSQLSERVER and SQLSERVERAGENT
.
Again it works fine if started from a dos command line but most inconvienent
not to have it start automatically or start from within the EM.
Any suggestions?
dmatta59|||Have resolved the problem. Used scm.exe to install the SQLServerAgent servi
ce using the instructions on the following article:
http://groups.google.com/groups?q=i...tngxa06&rnum=21
**Please note that the in this case the sqlagent -c -v was working from the
dos prompt and the jobs could run properly. The only problem was that the S
QLServerAgent was not automatically starting or couldn't be started within E
M.
Thank you,
dmatta59

missing tables and stored procedures after restoring database

I have been running a desktop PC with MSDE 1.0 installed. I had made a
backup of the data using a t-sql command backup database ... Since this PC
had crashed and has subsequently been rebuilt, I have restored the database
but found that vital tables and stored procedures are missing. The missing
tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
into the database as user sa.
Any help in recovering those missing tables and stored procedures would be
greatly appreciated.
use restore headeronly command on the backup file To check when the
backup was taken looks like you haven't backed up the database when
you created the tables whcih you said you were missing or you have
restored
an earlier backup not the latest once since you are the Sysadmin u can
view all the tables created with any login and if you want to have
information
about the latest backup taken check out the one with
Use Msdb
select *from backupset
order by backup_finish_date desc
|||If they're missing after a restore then they were not there at the time
of the back and are now gone forever (presumedly they were created after
the backup you used to restore the DB). Do you have any later backups?
BTW, every table & proc in a DB has an owner. To be sure you're just
not missing it in whatever client-side tool you're using execute this T-SQL:
select o.[name] as tablename, u.[name] as ownername, type
from dbo.sysobjects as o
inner join dbo.sysusers as u on o.uid = o.uid
order by type, u.[name], o.[name]
Have a look to see if you can see the proc (type P) or the table (type
U) somewhere in the resultset. Also are you sure these "vital" tables &
procs were in the same database and weren't in another database that was
being referenced from your database? For example,
use A
go
select * from B.dbo.MyVitalTable
exec B.dbo.MyVitalProc
If that was true then they wouldn't be included in the backup (and
therefore subsequent restore) of your database.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Old Paulie wrote:

>I have been running a desktop PC with MSDE 1.0 installed. I had made a
>backup of the data using a t-sql command backup database ... Since this PC
>had crashed and has subsequently been rebuilt, I have restored the database
>but found that vital tables and stored procedures are missing. The missing
>tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
>into the database as user sa.
>Any help in recovering those missing tables and stored procedures would be
>greatly appreciated.
>
|||saradhi,
Thanks for the advice, I have checked the backupset table in the Msdb
database and that only describes one backup taken last year. The backup at
that time probably would not have included these missing tables. I had
however made several backups and their is no proof of these in this table. I
need to obviously review the way I back up since it appears I am doing
something fundamentally wrong. Any advice on backing up for future reference
would be greatly appreciated. Should I be backing up the other databases
that are created upon install of msde, ie Master, Msdb etc ...?
"saradhi" wrote:

> use restore headeronly command on the backup file To check when the
> backup was taken looks like you haven't backed up the database when
> you created the tables whcih you said you were missing or you have
> restored
> an earlier backup not the latest once since you are the Sysadmin u can
> view all the tables created with any login and if you want to have
> information
> about the latest backup taken check out the one with
> Use Msdb
> select *from backupset
> order by backup_finish_date desc
>
|||Hi Mike,
I am quite sure that the vital tables belonged to my database as I had
created no others! I did run your query and did not find and records
relating to the missing tables and stored procedures. From your advice and
'saradhi's', it is obvious now that my backup was flawed and I am doing
something wrong Thank you for your assistance.
"Mike Hodgson" wrote:
[vbcol=seagreen]
> If they're missing after a restore then they were not there at the time
> of the back and are now gone forever (presumedly they were created after
> the backup you used to restore the DB). Do you have any later backups?
> BTW, every table & proc in a DB has an owner. To be sure you're just
> not missing it in whatever client-side tool you're using execute this T-SQL:
> select o.[name] as tablename, u.[name] as ownername, type
> from dbo.sysobjects as o
> inner join dbo.sysusers as u on o.uid = o.uid
> order by type, u.[name], o.[name]
> Have a look to see if you can see the proc (type P) or the table (type
> U) somewhere in the resultset. Also are you sure these "vital" tables &
> procs were in the same database and weren't in another database that was
> being referenced from your database? For example,
> use A
> go
> select * from B.dbo.MyVitalTable
> exec B.dbo.MyVitalProc
> If that was true then they wouldn't be included in the backup (and
> therefore subsequent restore) of your database.
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Old Paulie wrote:
|||One last chance. Perhaps your backup file has several backups on it, and you restore the first one?
Check using RESTORE HEADERONLY.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Old Paulie" <OldPaulie@.discussions.microsoft.com> wrote in message
news:BADA21C1-5F74-4E9A-83FD-779132C78585@.microsoft.com...[vbcol=seagreen]
> Hi Mike,
> I am quite sure that the vital tables belonged to my database as I had
> created no others! I did run your query and did not find and records
> relating to the missing tables and stored procedures. From your advice and
> 'saradhi's', it is obvious now that my backup was flawed and I am doing
> something wrong Thank you for your assistance.
> "Mike Hodgson" wrote:
|||Tibor,
It turns out that my backup DID include several backup sets and I was
therefore able to restore the most recent backup set to get back all missing
tables and procedures.
THANK YOU VERY MUCH!
"Tibor Karaszi" wrote:

> One last chance. Perhaps your backup file has several backups on it, and you restore the first one?
> Check using RESTORE HEADERONLY.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Old Paulie" <OldPaulie@.discussions.microsoft.com> wrote in message
> news:BADA21C1-5F74-4E9A-83FD-779132C78585@.microsoft.com...
>

missing tables and stored procedures after restoring database

I have been running a desktop PC with MSDE 1.0 installed. I had made a
backup of the data using a t-sql command backup database ... Since this PC
had crashed and has subsequently been rebuilt, I have restored the database
but found that vital tables and stored procedures are missing. The missing
tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
into the database as user sa.
Any help in recovering those missing tables and stored procedures would be
greatly appreciated.use restore headeronly command on the backup file To check when the
backup was taken looks like you haven't backed up the database when
you created the tables whcih you said you were missing or you have
restored
an earlier backup not the latest once since you are the Sysadmin u can
view all the tables created with any login and if you want to have
information
about the latest backup taken check out the one with
Use Msdb
select *from backupset
order by backup_finish_date desc|||If they're missing after a restore then they were not there at the time
of the back and are now gone forever (presumedly they were created after
the backup you used to restore the DB). Do you have any later backups?
BTW, every table & proc in a DB has an owner. To be sure you're just
not missing it in whatever client-side tool you're using execute this T-SQL:
select o.[name] as tablename, u.[name] as ownername, type
from dbo.sysobjects as o
inner join dbo.sysusers as u on o.uid = o.uid
order by type, u.[name], o.[name]
Have a look to see if you can see the proc (type P) or the table (type
U) somewhere in the resultset. Also are you sure these "vital" tables &
procs were in the same database and weren't in another database that was
being referenced from your database? For example,
use A
go
select * from B.dbo.MyVitalTable
exec B.dbo.MyVitalProc
If that was true then they wouldn't be included in the backup (and
therefore subsequent restore) of your database.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Old Paulie wrote:

>I have been running a desktop PC with MSDE 1.0 installed. I had made a
>backup of the data using a t-sql command backup database ... Since this PC
>had crashed and has subsequently been rebuilt, I have restored the database
>but found that vital tables and stored procedures are missing. The missing
>tables were not allegedly owned by dbo but perhaps had no owner(?) PS I lo
g
>into the database as user sa.
>Any help in recovering those missing tables and stored procedures would be
>greatly appreciated.
>|||saradhi,
Thanks for the advice, I have checked the backupset table in the Msdb
database and that only describes one backup taken last year. The backup at
that time probably would not have included these missing tables. I had
however made several backups and their is no proof of these in this table.
I
need to obviously review the way I back up since it appears I am doing
something fundamentally wrong. Any advice on backing up for future referenc
e
would be greatly appreciated. Should I be backing up the other databases
that are created upon install of msde, ie Master, Msdb etc ...?
"saradhi" wrote:

> use restore headeronly command on the backup file To check when the
> backup was taken looks like you haven't backed up the database when
> you created the tables whcih you said you were missing or you have
> restored
> an earlier backup not the latest once since you are the Sysadmin u can
> view all the tables created with any login and if you want to have
> information
> about the latest backup taken check out the one with
> Use Msdb
> select *from backupset
> order by backup_finish_date desc
>|||Hi Mike,
I am quite sure that the vital tables belonged to my database as I had
created no others! I did run your query and did not find and records
relating to the missing tables and stored procedures. From your advice and
'saradhi's', it is obvious now that my backup was flawed and I am doing
something wrong Thank you for your assistance.
"Mike Hodgson" wrote:
[vbcol=seagreen]
> If they're missing after a restore then they were not there at the time
> of the back and are now gone forever (presumedly they were created after
> the backup you used to restore the DB). Do you have any later backups?
> BTW, every table & proc in a DB has an owner. To be sure you're just
> not missing it in whatever client-side tool you're using execute this T-SQ
L:
> select o.[name] as tablename, u.[name] as ownername, type
> from dbo.sysobjects as o
> inner join dbo.sysusers as u on o.uid = o.uid
> order by type, u.[name], o.[name]
> Have a look to see if you can see the proc (type P) or the table (type
> U) somewhere in the resultset. Also are you sure these "vital" tables &
> procs were in the same database and weren't in another database that was
> being referenced from your database? For example,
> use A
> go
> select * from B.dbo.MyVitalTable
> exec B.dbo.MyVitalProc
> If that was true then they wouldn't be included in the backup (and
> therefore subsequent restore) of your database.
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Old Paulie wrote:
>|||One last chance. Perhaps your backup file has several backups on it, and you
restore the first one?
Check using RESTORE HEADERONLY.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Old Paulie" <OldPaulie@.discussions.microsoft.com> wrote in message
news:BADA21C1-5F74-4E9A-83FD-779132C78585@.microsoft.com...[vbcol=seagreen]
> Hi Mike,
> I am quite sure that the vital tables belonged to my database as I had
> created no others! I did run your query and did not find and records
> relating to the missing tables and stored procedures. From your advice an
d
> 'saradhi's', it is obvious now that my backup was flawed and I am doing
> something wrong Thank you for your assistance.
> "Mike Hodgson" wrote:
>|||Tibor,
It turns out that my backup DID include several backup sets and I was
therefore able to restore the most recent backup set to get back all missing
tables and procedures.
THANK YOU VERY MUCH!
"Tibor Karaszi" wrote:

> One last chance. Perhaps your backup file has several backups on it, and y
ou restore the first one?
> Check using RESTORE HEADERONLY.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Old Paulie" <OldPaulie@.discussions.microsoft.com> wrote in message
> news:BADA21C1-5F74-4E9A-83FD-779132C78585@.microsoft.com...
>

missing tables and stored procedures after restoring database

I have been running a desktop PC with MSDE 1.0 installed. I had made a
backup of the data using a t-sql command backup database ... Since this PC
had crashed and has subsequently been rebuilt, I have restored the database
but found that vital tables and stored procedures are missing. The missing
tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
into the database as user sa.
Any help in recovering those missing tables and stored procedures would be
greatly appreciated.use restore headeronly command on the backup file To check when the
backup was taken looks like you haven't backed up the database when
you created the tables whcih you said you were missing or you have
restored
an earlier backup not the latest once since you are the Sysadmin u can
view all the tables created with any login and if you want to have
information
about the latest backup taken check out the one with
Use Msdb
select *from backupset
order by backup_finish_date desc|||This is a multi-part message in MIME format.
--080807080807040609090709
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
If they're missing after a restore then they were not there at the time
of the back and are now gone forever (presumedly they were created after
the backup you used to restore the DB). Do you have any later backups?
BTW, every table & proc in a DB has an owner. To be sure you're just
not missing it in whatever client-side tool you're using execute this T-SQL:
select o.[name] as tablename, u.[name] as ownername, type
from dbo.sysobjects as o
inner join dbo.sysusers as u on o.uid = o.uid
order by type, u.[name], o.[name]
Have a look to see if you can see the proc (type P) or the table (type
U) somewhere in the resultset. Also are you sure these "vital" tables &
procs were in the same database and weren't in another database that was
being referenced from your database? For example,
use A
go
select * from B.dbo.MyVitalTable
exec B.dbo.MyVitalProc
If that was true then they wouldn't be included in the backup (and
therefore subsequent restore) of your database.
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Old Paulie wrote:
>I have been running a desktop PC with MSDE 1.0 installed. I had made a
>backup of the data using a t-sql command backup database ... Since this PC
>had crashed and has subsequently been rebuilt, I have restored the database
>but found that vital tables and stored procedures are missing. The missing
>tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
>into the database as user sa.
>Any help in recovering those missing tables and stored procedures would be
>greatly appreciated.
>
--080807080807040609090709
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>If they're missing after a restore then they were not there at the
time of the back and are now gone forever (presumedly they were created
after the backup you used to restore the DB). Do you have any later
backups?<br>
<br>
BTW, every table & proc in a DB has an owner. To be sure you're
just not missing it in whatever client-side tool you're using execute
this T-SQL:<br>
</tt>
<blockquote><tt>select o.[name] as tablename, u.[name] as ownername,
type<br>
from dbo.sysobjects as o<br>
   inner join dbo.sysusers as u on o.uid = o.uid<br>
order by type, u.[name], o.[name]<br>
</tt></blockquote>
<tt>Have a look to see if you can see the proc (type P) or the table
(type U) somewhere in the resultset. Also are you sure these "vital"
tables & procs were in the same database and weren't in another
database that was being referenced from your database? For example,<br>
</tt>
<blockquote><tt>use A<br>
go<br>
<br>
select * from B.dbo.MyVitalTable<br>
exec B.dbo.MyVitalProc<br>
</tt></blockquote>
<tt>If that was true then they wouldn't be included in the backup (and
therefore subsequent restore) of your database.</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Old Paulie wrote:
<blockquote cite="mid99FCEEAA-D592-4D73-AD2D-946AD7C71952@.microsoft.com"
type="cite">
<pre wrap="">I have been running a desktop PC with MSDE 1.0 installed. I had made a
backup of the data using a t-sql command backup database ... Since this PC
had crashed and has subsequently been rebuilt, I have restored the database
but found that vital tables and stored procedures are missing. The missing
tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
into the database as user sa.
Any help in recovering those missing tables and stored procedures would be
greatly appreciated.
</pre>
</blockquote>
</body>
</html>
--080807080807040609090709--|||saradhi,
Thanks for the advice, I have checked the backupset table in the Msdb
database and that only describes one backup taken last year. The backup at
that time probably would not have included these missing tables. I had
however made several backups and their is no proof of these in this table. I
need to obviously review the way I back up since it appears I am doing
something fundamentally wrong. Any advice on backing up for future reference
would be greatly appreciated. Should I be backing up the other databases
that are created upon install of msde, ie Master, Msdb etc ...?
"saradhi" wrote:
> use restore headeronly command on the backup file To check when the
> backup was taken looks like you haven't backed up the database when
> you created the tables whcih you said you were missing or you have
> restored
> an earlier backup not the latest once since you are the Sysadmin u can
> view all the tables created with any login and if you want to have
> information
> about the latest backup taken check out the one with
> Use Msdb
> select *from backupset
> order by backup_finish_date desc
>|||Hi Mike,
I am quite sure that the vital tables belonged to my database as I had
created no others! I did run your query and did not find and records
relating to the missing tables and stored procedures. From your advice and
'saradhi's', it is obvious now that my backup was flawed and I am doing
something wrong:( Thank you for your assistance.
"Mike Hodgson" wrote:
> If they're missing after a restore then they were not there at the time
> of the back and are now gone forever (presumedly they were created after
> the backup you used to restore the DB). Do you have any later backups?
> BTW, every table & proc in a DB has an owner. To be sure you're just
> not missing it in whatever client-side tool you're using execute this T-SQL:
> select o.[name] as tablename, u.[name] as ownername, type
> from dbo.sysobjects as o
> inner join dbo.sysusers as u on o.uid = o.uid
> order by type, u.[name], o.[name]
> Have a look to see if you can see the proc (type P) or the table (type
> U) somewhere in the resultset. Also are you sure these "vital" tables &
> procs were in the same database and weren't in another database that was
> being referenced from your database? For example,
> use A
> go
> select * from B.dbo.MyVitalTable
> exec B.dbo.MyVitalProc
> If that was true then they wouldn't be included in the backup (and
> therefore subsequent restore) of your database.
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> Old Paulie wrote:
> >I have been running a desktop PC with MSDE 1.0 installed. I had made a
> >backup of the data using a t-sql command backup database ... Since this PC
> >had crashed and has subsequently been rebuilt, I have restored the database
> >but found that vital tables and stored procedures are missing. The missing
> >tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
> >into the database as user sa.
> >
> >Any help in recovering those missing tables and stored procedures would be
> >greatly appreciated|||One last chance. Perhaps your backup file has several backups on it, and you restore the first one?
Check using RESTORE HEADERONLY.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Old Paulie" <OldPaulie@.discussions.microsoft.com> wrote in message
news:BADA21C1-5F74-4E9A-83FD-779132C78585@.microsoft.com...
> Hi Mike,
> I am quite sure that the vital tables belonged to my database as I had
> created no others! I did run your query and did not find and records
> relating to the missing tables and stored procedures. From your advice and
> 'saradhi's', it is obvious now that my backup was flawed and I am doing
> something wrong:( Thank you for your assistance.
> "Mike Hodgson" wrote:
>> If they're missing after a restore then they were not there at the time
>> of the back and are now gone forever (presumedly they were created after
>> the backup you used to restore the DB). Do you have any later backups?
>> BTW, every table & proc in a DB has an owner. To be sure you're just
>> not missing it in whatever client-side tool you're using execute this T-SQL:
>> select o.[name] as tablename, u.[name] as ownername, type
>> from dbo.sysobjects as o
>> inner join dbo.sysusers as u on o.uid = o.uid
>> order by type, u.[name], o.[name]
>> Have a look to see if you can see the proc (type P) or the table (type
>> U) somewhere in the resultset. Also are you sure these "vital" tables &
>> procs were in the same database and weren't in another database that was
>> being referenced from your database? For example,
>> use A
>> go
>> select * from B.dbo.MyVitalTable
>> exec B.dbo.MyVitalProc
>> If that was true then they wouldn't be included in the backup (and
>> therefore subsequent restore) of your database.
>> --
>> *mike hodgson*
>> blog: http://sqlnerd.blogspot.com
>>
>> Old Paulie wrote:
>> >I have been running a desktop PC with MSDE 1.0 installed. I had made a
>> >backup of the data using a t-sql command backup database ... Since this PC
>> >had crashed and has subsequently been rebuilt, I have restored the database
>> >but found that vital tables and stored procedures are missing. The missing
>> >tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
>> >into the database as user sa.
>> >
>> >Any help in recovering those missing tables and stored procedures would be
>> >greatly appreciated|||Tibor,
It turns out that my backup DID include several backup sets and I was
therefore able to restore the most recent backup set to get back all missing
tables and procedures.
THANK YOU VERY MUCH!
"Tibor Karaszi" wrote:
> One last chance. Perhaps your backup file has several backups on it, and you restore the first one?
> Check using RESTORE HEADERONLY.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Old Paulie" <OldPaulie@.discussions.microsoft.com> wrote in message
> news:BADA21C1-5F74-4E9A-83FD-779132C78585@.microsoft.com...
> > Hi Mike,
> >
> > I am quite sure that the vital tables belonged to my database as I had
> > created no others! I did run your query and did not find and records
> > relating to the missing tables and stored procedures. From your advice and
> > 'saradhi's', it is obvious now that my backup was flawed and I am doing
> > something wrong:( Thank you for your assistance.
> >
> > "Mike Hodgson" wrote:
> >
> >> If they're missing after a restore then they were not there at the time
> >> of the back and are now gone forever (presumedly they were created after
> >> the backup you used to restore the DB). Do you have any later backups?
> >>
> >> BTW, every table & proc in a DB has an owner. To be sure you're just
> >> not missing it in whatever client-side tool you're using execute this T-SQL:
> >>
> >> select o.[name] as tablename, u.[name] as ownername, type
> >> from dbo.sysobjects as o
> >> inner join dbo.sysusers as u on o.uid = o.uid
> >> order by type, u.[name], o.[name]
> >>
> >> Have a look to see if you can see the proc (type P) or the table (type
> >> U) somewhere in the resultset. Also are you sure these "vital" tables &
> >> procs were in the same database and weren't in another database that was
> >> being referenced from your database? For example,
> >>
> >> use A
> >> go
> >>
> >> select * from B.dbo.MyVitalTable
> >> exec B.dbo.MyVitalProc
> >>
> >> If that was true then they wouldn't be included in the backup (and
> >> therefore subsequent restore) of your database.
> >>
> >> --
> >> *mike hodgson*
> >> blog: http://sqlnerd.blogspot.com
> >>
> >>
> >>
> >> Old Paulie wrote:
> >>
> >> >I have been running a desktop PC with MSDE 1.0 installed. I had made a
> >> >backup of the data using a t-sql command backup database ... Since this PC
> >> >had crashed and has subsequently been rebuilt, I have restored the database
> >> >but found that vital tables and stored procedures are missing. The missing
> >> >tables were not allegedly owned by dbo but perhaps had no owner(?) PS I log
> >> >into the database as user sa.
> >> >
> >> >Any help in recovering those missing tables and stored procedures would be
> >> >greatly appreciated
>

Missing Subject

Hi,
last month I installed SQL Server 2000 on a new server (Install SQL2000 and
then upgraded to SP4) because that server is going to replace the main
production server. I've restored the database dumps from the old server to
the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
because there are some stored procedures that use the xp_sendmail.
Everything seems to work OK, until I noticed that the mails, sent by SQL
Mail using the xp_sendmail are all missing the subject line, whereas the
subject line is present in the mail sent by the (old) production server.
the code in the stored procedures that invoke xp_sendmail is identical on
both machines.
Am I missing something or...
--
Adri
Programmers do it Bit by BitHi
Without seeing the actual call to xp_sendmail it is hard to say, but at a
guess you are possibly concatentating to a NULL value or something similar
either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
different.
John
"Adri" wrote:
> Hi,
> last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> then upgraded to SP4) because that server is going to replace the main
> production server. I've restored the database dumps from the old server to
> the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> because there are some stored procedures that use the xp_sendmail.
> Everything seems to work OK, until I noticed that the mails, sent by SQL
> Mail using the xp_sendmail are all missing the subject line, whereas the
> subject line is present in the mail sent by the (old) production server.
> the code in the stored procedures that invoke xp_sendmail is identical on
> both machines.
> Am I missing something or...
> --
> Adri
> Programmers do it Bit by Bit|||Adri skrev:
> ...
> Am I missing something or...
> ...
Actually yes, the Subject ;)|||In fact, a simple
xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
,@.subject = 'subject'
delivers an e-mail with an empty subject line :-(
--
Adri
Programmers do it Bit by Bit
"John Bell" wrote:
> Hi
> Without seeing the actual call to xp_sendmail it is hard to say, but at a
> guess you are possibly concatentating to a NULL value or something similar
> either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
> different.
> John
> "Adri" wrote:
> > Hi,
> >
> > last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> > then upgraded to SP4) because that server is going to replace the main
> > production server. I've restored the database dumps from the old server to
> > the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> > because there are some stored procedures that use the xp_sendmail.
> >
> > Everything seems to work OK, until I noticed that the mails, sent by SQL
> > Mail using the xp_sendmail are all missing the subject line, whereas the
> > subject line is present in the mail sent by the (old) production server.
> >
> > the code in the stored procedures that invoke xp_sendmail is identical on
> > both machines.
> >
> > Am I missing something or...
> > --
> > Adri
> > Programmers do it Bit by Bit|||Hi Adri
More questions...
I assume you can send mail successfully from Outlook with a subject? if the
subject parameter is before the message parameter does it work? Is this 32 or
64 bit?
John
"Adri" wrote:
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
>
> "John Bell" wrote:
> > Hi
> >
> > Without seeing the actual call to xp_sendmail it is hard to say, but at a
> > guess you are possibly concatentating to a NULL value or something similar
> > either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
> > different.
> >
> > John
> >
> > "Adri" wrote:
> >
> > > Hi,
> > >
> > > last month I installed SQL Server 2000 on a new server (Install SQL2000 and
> > > then upgraded to SP4) because that server is going to replace the main
> > > production server. I've restored the database dumps from the old server to
> > > the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
> > > because there are some stored procedures that use the xp_sendmail.
> > >
> > > Everything seems to work OK, until I noticed that the mails, sent by SQL
> > > Mail using the xp_sendmail are all missing the subject line, whereas the
> > > subject line is present in the mail sent by the (old) production server.
> > >
> > > the code in the stored procedures that invoke xp_sendmail is identical on
> > > both machines.
> > >
> > > Am I missing something or...
> > > --
> > > Adri
> > > Programmers do it Bit by Bit|||Adri wrote:
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
*bonk*
Sorry for my pityful attempt of being funny :) I actually didn't read
your post carefully enough and didn't realize your problem was really
'Missing Subject', not that some client added that as a subject for
your post (that you had sent without a subject)... Ahem...
Btw, did you do a search on Google, I saw a lot of hits using
"xp_sendmail" and "subject" as search parameters even though I didn't
instantly find a solution for the problem...
/impslayer, aka Birger Johansson|||Hi Adri,
My understanding of your issue is:
After the migration of SQL Server 2000 from an older server to a new one,
you can also send email by xp_sendmail in your stored procedures,however
those sent mails' subjects are missed.
If I have misunderstood, please let me know.
I recommend that you try the following:
1) Login as account that is running SQL Server server and open outlook.
2) Tools->Options->Mail Format tab. Change the "compose in message format"
to plan
text and send an email through outlook with a subject.
3) Change the "compose in message format" back to html. Send email with
subject.
Stop and start SQL Server instance might be necessary.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi Charles,
In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
SQL from RTM to SP4. Having done that, I restored the (user)database dumps
from the old server to the new one, and configured SQL Mail as usual.
The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
Hotfix KB891640 applied and at last upgraded to SP4.
I've changed the Mail Format as you supposed, but that did not help.
--
Adri
Programmers do it Bit by Bit
"Charles Wang[MSFT]" wrote:
> Hi Adri,
> My understanding of your issue is:
> After the migration of SQL Server 2000 from an older server to a new one,
> you can also send email by xp_sendmail in your stored procedures,however
> those sent mails' subjects are missed.
> If I have misunderstood, please let me know.
> I recommend that you try the following:
> 1) Login as account that is running SQL Server server and open outlook.
> 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> to plan
> text and send an email through outlook with a subject.
> 3) Change the "compose in message format" back to html. Send email with
> subject.
> Stop and start SQL Server instance might be necessary.
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>|||Like saying "This page is intentionally blank"!!!
John
"impslayer" wrote:
> Adri wrote:
> > In fact, a simple
> >
> > xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
> > ,@.subject = 'subject'
> >
> > delivers an e-mail with an empty subject line :-(
> >
> > --
> > Adri
> > Programmers do it Bit by Bit
> *bonk*
> Sorry for my pityful attempt of being funny :) I actually didn't read
> your post carefully enough and didn't realize your problem was really
> 'Missing Subject', not that some client added that as a subject for
> your post (that you had sent without a subject)... Ahem...
> Btw, did you do a search on Google, I saw a lot of hits using
> "xp_sendmail" and "subject" as search parameters even though I didn't
> instantly find a solution for the problem...
> /impslayer, aka Birger Johansson
>|||Hi Adri,
To make sure this is a dabase wide issue or server instance side issue, I
recommend that you create a new stored procedure with xp_sendmail in a test
database and see whether or not it has the same issue.
Also, you may try recompiling the stored procedures.
Charles Wang
Microsoft Online Community Support|||Hi
Please clarify that using Outlook directly is working ok?
Which version of office is being used?
John
"Adri" wrote:
> Hi Charles,
> In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
> SQL from RTM to SP4. Having done that, I restored the (user)database dumps
> from the old server to the new one, and configured SQL Mail as usual.
> The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
> Hotfix KB891640 applied and at last upgraded to SP4.
> I've changed the Mail Format as you supposed, but that did not help.
> --
> Adri
> Programmers do it Bit by Bit
>
> "Charles Wang[MSFT]" wrote:
> > Hi Adri,
> >
> > My understanding of your issue is:
> > After the migration of SQL Server 2000 from an older server to a new one,
> > you can also send email by xp_sendmail in your stored procedures,however
> > those sent mails' subjects are missed.
> > If I have misunderstood, please let me know.
> >
> > I recommend that you try the following:
> > 1) Login as account that is running SQL Server server and open outlook.
> > 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> > to plan
> > text and send an email through outlook with a subject.
> > 3) Change the "compose in message format" back to html. Send email with
> > subject.
> >
> > Stop and start SQL Server instance might be necessary.
> >
> > Sincerely yours,
> > Charles Wang
> > Microsoft Online Community Support
> > ======================================================> > When responding to posts, please "Reply to Group" via
> > your newsreader so that others may learn and benefit
> > from this issue.
> > ======================================================> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > ======================================================> >
> >
> >

Missing Subject

Hi,
last month I installed SQL Server 2000 on a new server (Install SQL2000 and
then upgraded to SP4) because that server is going to replace the main
production server. I've restored the database dumps from the old server to
the new one and did also copy the SQL Agent jobs. Also configured SQL Mail,
because there are some stored procedures that use the xp_sendmail.
Everything seems to work OK, until I noticed that the mails, sent by SQL
Mail using the xp_sendmail are all missing the subject line, whereas the
subject line is present in the mail sent by the (old) production server.
the code in the stored procedures that invoke xp_sendmail is identical on
both machines.
Am I missing something or...
--
Adri
Programmers do it Bit by BitHi
Without seeing the actual call to xp_sendmail it is hard to say, but at a
guess you are possibly concatentating to a NULL value or something similar
either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
different.
John
"Adri" wrote:

> Hi,
> last month I installed SQL Server 2000 on a new server (Install SQL2000 an
d
> then upgraded to SP4) because that server is going to replace the main
> production server. I've restored the database dumps from the old server to
> the new one and did also copy the SQL Agent jobs. Also configured SQL Mail
,
> because there are some stored procedures that use the xp_sendmail.
> Everything seems to work OK, until I noticed that the mails, sent by SQL
> Mail using the xp_sendmail are all missing the subject line, whereas the
> subject line is present in the mail sent by the (old) production server.
> the code in the stored procedures that invoke xp_sendmail is identical on
> both machines.
> Am I missing something or...
> --
> Adri
> Programmers do it Bit by Bit|||Adri skrev:

> ...
> Am I missing something or...
> ...
Actually yes, the Subject ;)|||In fact, a simple
xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message'
,@.subject = 'subject'
delivers an e-mail with an empty subject line :-(
Adri
Programmers do it Bit by Bit
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Without seeing the actual call to xp_sendmail it is hard to say, but at a
> guess you are possibly concatentating to a NULL value or something similar
> either because the data is different or may be CONCAT_NULL_YIELDS_NULL is
> different.
> John
> "Adri" wrote:
>|||Hi Adri
More questions...
I assume you can send mail successfully from Outlook with a subject? if the
subject parameter is before the message parameter does it work? Is this 32 o
r
64 bit?
John
"Adri" wrote:
[vbcol=seagreen]
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message
'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
>
> "John Bell" wrote:
>|||Adri wrote:
> In fact, a simple
> xp_sendmail @.recipients = 'someuser@.somedomain.where' ,@.message = 'message
'
> ,@.subject = 'subject'
> delivers an e-mail with an empty subject line :-(
> --
> Adri
> Programmers do it Bit by Bit
*bonk*
Sorry for my pityful attempt of being funny I actually didn't read
your post carefully enough and didn't realize your problem was really
'Missing Subject', not that some client added that as a subject for
your post (that you had sent without a subject)... Ahem...
Btw, did you do a search on Google, I saw a lot of hits using
"xp_sendmail" and "subject" as search parameters even though I didn't
instantly find a solution for the problem...
/impslayer, aka Birger Johansson|||Hi Adri,
My understanding of your issue is:
After the migration of SQL Server 2000 from an older server to a new one,
you can also send email by xp_sendmail in your stored procedures,however
those sent mails' subjects are missed.
If I have misunderstood, please let me know.
I recommend that you try the following:
1) Login as account that is running SQL Server server and open outlook.
2) Tools->Options->Mail Format tab. Change the "compose in message format"
to plan
text and send an email through outlook with a subject.
3) Change the "compose in message format" back to html. Send email with
subject.
Stop and start SQL Server instance might be necessary.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi Charles,
In fact, I did a new installation of SQL 2000 on a W2K3 server and upgraded
SQL from RTM to SP4. Having done that, I restored the (user)database dumps
from the old server to the new one, and configured SQL Mail as usual.
The old server had originally SQL 2000 RTM installed, upgraded to SP2, SP3,
Hotfix KB891640 applied and at last upgraded to SP4.
I've changed the Mail Format as you supposed, but that did not help.
--
Adri
Programmers do it Bit by Bit
"Charles Wang[MSFT]" wrote:

> Hi Adri,
> My understanding of your issue is:
> After the migration of SQL Server 2000 from an older server to a new one,
> you can also send email by xp_sendmail in your stored procedures,however
> those sent mails' subjects are missed.
> If I have misunderstood, please let me know.
> I recommend that you try the following:
> 1) Login as account that is running SQL Server server and open outlook.
> 2) Tools->Options->Mail Format tab. Change the "compose in message format"
> to plan
> text and send an email through outlook with a subject.
> 3) Change the "compose in message format" back to html. Send email with
> subject.
> Stop and start SQL Server instance might be necessary.
> Sincerely yours,
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>|||Like saying "This page is intentionally blank"!!!
John
"impslayer" wrote:

> Adri wrote:
> *bonk*
> Sorry for my pityful attempt of being funny I actually didn't read
> your post carefully enough and didn't realize your problem was really
> 'Missing Subject', not that some client added that as a subject for
> your post (that you had sent without a subject)... Ahem...
> Btw, did you do a search on Google, I saw a lot of hits using
> "xp_sendmail" and "subject" as search parameters even though I didn't
> instantly find a solution for the problem...
> /impslayer, aka Birger Johansson
>|||Hi Adri,
To make sure this is a dabase wide issue or server instance side issue, I
recommend that you create a new stored procedure with xp_sendmail in a test
database and see whether or not it has the same issue.
Also, you may try recompiling the stored procedures.
Charles Wang
Microsoft Online Community Support

Missing SQL Server Project template

I have VS2005 Beta 2 (build 8.0.50215.44) and the June CTP of SQL Server 2005 Developer Edition installed.

Within VS2005, when I go to File -> New Project, I don't have the "Database" project type under either VB or C#. Which also means that the "SQL Server Project" template is not being offered.

Is there a manual way of adding the template, or some other workaround/solution?

Which SKU of Visual Studio are you using? Visual Studio Express does not have SQL Server project support.

Thanks,
-Vineet.

|||It's the full version of Visual Studio 2005, Beta 2, that was released in mid April.|||Actually database projects are not availble in VS Express and VS Standard editions. It sounds like that is what you have. Can you confirm?|||Which editions of VS.Net 2005 do have the "SQL Server" project templates? Or can they be downloaded from somewhere? (I have not been able to find such a place...)
Many thanks.
|||Nevermind. I have VS.Net 2005 Beta2 and didn't notice that if I expanded the Visual C# under the project types tree, there was a database node which contained the "SQL Server" project template.
Take care.

Missing Sql Server node

I have just installed Visual Studio 2005 team system beta 2 on an XP machine which had a sql server 2000 previously installed. However I do not see the Sql Servers node in Solution explorer. I do have the data connections node and can make conenctions to the server. Does anyone know what I can do to make the Sql Servers node available?

Hi Asim Shah,

You should register again almost one SQL Server there.

Good Coding!

Javier Luna
http://guydotnetxmlwebservices.blogspot.com/

Missing Sql Server node

I have just installed Visual Studio 2005 team system beta 2 on an XP machine which had a sql server 2000 previously installed. However I do not see the Sql Servers node in Solution explorer. I do have the data connections node and can make conenctions to the server. Does anyone know what I can do to make the Sql Servers node available?

Hi Asim Shah,

You should register again almost one SQL Server there.

Good Coding!

Javier Luna
http://guydotnetxmlwebservices.blogspot.com/

missing SQL Server Agent

Hi,

I'm learning SQL 2005 and installed the express ADV edition to my pc. But I miss the Agent service.

Is this included in express? Has it another name after SQL server 2000?

thanks

majid

Looking at the edition comparison page (http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx), it looks like SQL Agent Job Scheduling Service only comes with Workgroup, Standard, and Enterprise.

Thanks,
Sam Lester (MSFT)|||

oh, I see, Thanx

majid

Missing SQL Server 2000 Performance Counters

I installed SQL Server 2000 w/SP4 on a x64 Windows 2003 OS. I found that I
did not have access to the SQL performance counters and it is the same on
other servers with the same combination. Has anyone run into this issue?
What's the solution to it? thanks.Hi Jason,
Thank you for your post.
I understand that you can not view the Performance Counters of SQL Server
on a 64bit OS. If I misunderstood your concern, please feel free to let me
know.
A 64-bit perfmon client app can view OS counters plus counters for any
application that has installed a 64-bit perfmon DLL (a 64-bit app can't
load a 32-bit DLL). This means that a 64-bit perfmon client app can see a
local 64-bit SQL instance's counters, but not counters for a local 32-bit
instance running in WOW64.
A possible workaround to this problem could be:
Please run "mmc /32 perfmon.msc" from Start-Run. Please let me know whether
you can see the perfmon counters for 32-bit sql server or not.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Missing SQL Server 2000 Performance Counters

I installed SQL Server 2000 w/SP4 on a x64 Windows 2003 OS. I found that I
did not have access to the SQL performance counters and it is the same on
other servers with the same combination. Has anyone run into this issue?
What's the solution to it? thanks.Hi Jason,
Thank you for your post.
I understand that you can not view the Performance Counters of SQL Server
on a 64bit OS. If I misunderstood your concern, please feel free to let me
know.
A 64-bit perfmon client app can view OS counters plus counters for any
application that has installed a 64-bit perfmon DLL (a 64-bit app can't
load a 32-bit DLL). This means that a 64-bit perfmon client app can see a
local 64-bit SQL instance's counters, but not counters for a local 32-bit
instance running in WOW64.
A possible workaround to this problem could be:
Please run "mmc /32 perfmon.msc" from Start-Run. Please let me know whether
you can see the perfmon counters for 32-bit sql server or not.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Since this thread is already closed, here is a link to it:
http://groups.google.co.uk/group/mi...5989f5fc6817daa
"I installed SQL Server 2000 w/SP4 on a x64 Windows 2003 OS. I found
that I
did not have access to the SQL performance counters and it is the same
on
other servers with the same combination. Has anyone run into this
issue?
What's the solution to it? thanks. "
We are having the same problem, and the posted work around does work:
"A possible workaround to this problem could be:
Please run "mmc /32 perfmon.msc" from Start-Run. Please let me know
whether
you can see the perfmon counters for 32-bit sql server or not. "
...But, that prevents us from being able to see the counters from our
own computers which makes troubleshooting emergencies much quicker than
having to log in to the server itself to perform this.
Does anyone know any way of being able to see these counters from a
remote computer?
Thanks.

Missing ReportViewer WebControl

Hello:
I'm trying to integrate reports with my .NET 1.1 application (using VS2003).
I've installed SQL Server Reporting Services 05 Standard Edition, yet I do
not see the ReportViewer control in the normal installation folder - in
fact, the only folder installed under Samples is Databases, containing the
sample tutorial databases.
Trying to patch the installation didnt obviously reveal where the file would
be installed from.
Any thoughts?
ThanksI just found this:
http://www.microsoft.com/downloads/details.aspx?familyid=8a166cac-758d-45c8-b637-dd7726e61367&displaylang=en
Which I *assume* contains my controls, but its not compatible with .NET 1.1.
So I'll rephrase my question :)
I have a .NET app with some forms that I'd like to provide direct links to
their Reporting Services counterparts in PDF format. I need to pass values
to the stored procedure parameters for each respective report, however. This
is the part I am unsure of.
I do not want the user to be prompted for values, because several of the
procedures contain values that the user will not know. Instead I was hoping
to pass these either within the report querystring, but I am not sure how to
do this. I thought the ReportViewer control would do the trick but it
appears it wont. I cannot convert the app to 2.0 because a significant
amount of time has already been invested in code and fixing compatibility
issues is not within our timeline.
Can anyone please provide me with a direction? Thank you.
"Elliot Rodriguez" <elliotrodriguezatgeemaildotcom> wrote in message
news:eZ5szc$YGHA.3936@.TK2MSFTNGP05.phx.gbl...
> Hello:
> I'm trying to integrate reports with my .NET 1.1 application (using
> VS2003).
> I've installed SQL Server Reporting Services 05 Standard Edition, yet I do
> not see the ReportViewer control in the normal installation folder - in
> fact, the only folder installed under Samples is Databases, containing the
> sample tutorial databases.
> Trying to patch the installation didnt obviously reveal where the file
> would be installed from.
> Any thoughts?
> Thanks
>|||You have two options. One is to use webservices. You get a stream back with
the format in PDF. You pass it all the parameters. The other option is to
use URL integration. You could embed the IE web control and give it the
appropriate URL. The URL string can specify rendering format as well as the
parameters.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Elliot Rodriguez" <elliotrodriguezatgeemaildotcom> wrote in message
news:u2Nu8h$YGHA.3328@.TK2MSFTNGP02.phx.gbl...
>I just found this:
> http://www.microsoft.com/downloads/details.aspx?familyid=8a166cac-758d-45c8-b637-dd7726e61367&displaylang=en
> Which I *assume* contains my controls, but its not compatible with .NET
> 1.1.
> So I'll rephrase my question :)
> I have a .NET app with some forms that I'd like to provide direct links to
> their Reporting Services counterparts in PDF format. I need to pass values
> to the stored procedure parameters for each respective report, however.
> This is the part I am unsure of.
> I do not want the user to be prompted for values, because several of the
> procedures contain values that the user will not know. Instead I was
> hoping to pass these either within the report querystring, but I am not
> sure how to do this. I thought the ReportViewer control would do the trick
> but it appears it wont. I cannot convert the app to 2.0 because a
> significant amount of time has already been invested in code and fixing
> compatibility issues is not within our timeline.
> Can anyone please provide me with a direction? Thank you.
> "Elliot Rodriguez" <elliotrodriguezatgeemaildotcom> wrote in message
> news:eZ5szc$YGHA.3936@.TK2MSFTNGP05.phx.gbl...
>> Hello:
>> I'm trying to integrate reports with my .NET 1.1 application (using
>> VS2003).
>> I've installed SQL Server Reporting Services 05 Standard Edition, yet I
>> do not see the ReportViewer control in the normal installation folder -
>> in fact, the only folder installed under Samples is Databases, containing
>> the sample tutorial databases.
>> Trying to patch the installation didnt obviously reveal where the file
>> would be installed from.
>> Any thoughts?
>> Thanks
>>
>|||Thanks Bruce. Do you have any resources you can recommend for using the
Webservice option? I've found a lot on basic stuff but thats about it.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ubDgtn$YGHA.4760@.TK2MSFTNGP03.phx.gbl...
> You have two options. One is to use webservices. You get a stream back
> with the format in PDF. You pass it all the parameters. The other option
> is to use URL integration. You could embed the IE web control and give it
> the appropriate URL. The URL string can specify rendering format as well
> as the parameters.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Elliot Rodriguez" <elliotrodriguezatgeemaildotcom> wrote in message
> news:u2Nu8h$YGHA.3328@.TK2MSFTNGP02.phx.gbl...
>>I just found this:
>> http://www.microsoft.com/downloads/details.aspx?familyid=8a166cac-758d-45c8-b637-dd7726e61367&displaylang=en
>> Which I *assume* contains my controls, but its not compatible with .NET
>> 1.1.
>> So I'll rephrase my question :)
>> I have a .NET app with some forms that I'd like to provide direct links
>> to their Reporting Services counterparts in PDF format. I need to pass
>> values to the stored procedure parameters for each respective report,
>> however. This is the part I am unsure of.
>> I do not want the user to be prompted for values, because several of the
>> procedures contain values that the user will not know. Instead I was
>> hoping to pass these either within the report querystring, but I am not
>> sure how to do this. I thought the ReportViewer control would do the
>> trick but it appears it wont. I cannot convert the app to 2.0 because a
>> significant amount of time has already been invested in code and fixing
>> compatibility issues is not within our timeline.
>> Can anyone please provide me with a direction? Thank you.
>> "Elliot Rodriguez" <elliotrodriguezatgeemaildotcom> wrote in message
>> news:eZ5szc$YGHA.3936@.TK2MSFTNGP05.phx.gbl...
>> Hello:
>> I'm trying to integrate reports with my .NET 1.1 application (using
>> VS2003).
>> I've installed SQL Server Reporting Services 05 Standard Edition, yet I
>> do not see the ReportViewer control in the normal installation folder -
>> in fact, the only folder installed under Samples is Databases,
>> containing the sample tutorial databases.
>> Trying to patch the installation didnt obviously reveal where the file
>> would be installed from.
>> Any thoughts?
>> Thanks
>>
>>
>