ok to remove guest from msdb?

BOL says "The guest user can be deleted and added to all databases
except master and tempdb, where it must always exist."
any reason for guest to be in msdb?
I usually remove guest from msdb, but to be more certain before posting this I asked around my MVP
and MCT colleagues. No one has experienced any bad effect from removing guest from msdb. Of course,
for a non-sysadmin to create jobs etc, you need to add that login to msdb, but the fact that you now
can control who can do what is a good thing, IMO (and might just be why you posted this in the first
place :-) ).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ch" <ch@.dontemailme.com> wrote in message news:41862F84.647BCB04@.dontemailme.com...
> BOL says "The guest user can be deleted and added to all databases
> except master and tempdb, where it must always exist."
> any reason for guest to be in msdb?

ok to remove guest from msdb?

BOL says "The guest user can be deleted and added to all databases
except master and tempdb, where it must always exist."
any reason for guest to be in msdb?I usually remove guest from msdb, but to be more certain before posting this
I asked around my MVP
and MCT colleagues. No one has experienced any bad effect from removing gues
t from msdb. Of course,
for a non-sysadmin to create jobs etc, you need to add that login to msdb, b
ut the fact that you now
can control who can do what is a good thing, IMO (and might just be why you
posted this in the first
place :-) ).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ch" <ch@.dontemailme.com> wrote in message news:41862F84.647BCB04@.dontemailme.com...eagreen">
> BOL says "The guest user can be deleted and added to all databases
> except master and tempdb, where it must always exist."
> any reason for guest to be in msdb?

ok to remove guest from msdb?

BOL says "The guest user can be deleted and added to all databases
except master and tempdb, where it must always exist."
any reason for guest to be in msdb?I usually remove guest from msdb, but to be more certain before posting this I asked around my MVP
and MCT colleagues. No one has experienced any bad effect from removing guest from msdb. Of course,
for a non-sysadmin to create jobs etc, you need to add that login to msdb, but the fact that you now
can control who can do what is a good thing, IMO (and might just be why you posted this in the first
place :-) ).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ch" <ch@.dontemailme.com> wrote in message news:41862F84.647BCB04@.dontemailme.com...
> BOL says "The guest user can be deleted and added to all databases
> except master and tempdb, where it must always exist."
> any reason for guest to be in msdb?

Office Web Components

Do the interactivity features of OWC client side exist with reporting
services?
Can we replace the work that we do now with OWC and lots of javascript with
RS?I've looked at trying to replicate the pivottable owc in reporting services
but rs just isn't for that, well not without a mega amount of programming.
What part of OWC are you using?
--
Tony Rogerson
SQL Server MVP
http://www.sqlserverfaq.com?mbr=21
(Create your own groups, Forum, FAQ's and a ton more)|||No, RS matrix and chart regions are not meant to replace OWC. As you would
understand it is difficult to implement the same functionality in HTML than
using ActiveX controls. However, you can integrate your OWC components to
run RS reports, e.g. when the lowest level in a dimension hierarchy is
reached.
One more thing. In RS OWC are used only when exporting the report to HTML
OWC format. When this happen, RS exports matrix regions as pivot tables,
charts as chart space objects. However, OWC is not linked to the data
source. Instead, the data is always restricted to the data that the report
query returns.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Mike B" <MikeB@.discussions.microsoft.com> wrote in message
news:D7C0A07C-527C-45AD-9ECE-614BBF123027@.microsoft.com...
> Do the interactivity features of OWC client side exist with reporting
> services?
> Can we replace the work that we do now with OWC and lots of javascript
with
> RS?

ODBC/OLEDB support for HTTP-based comms to SQL server?

Does there exist an ODBC or OLEDB/ADODB driver for talking to SQL
server over HTTP/port 80?
In other words, I want to be able to issue SQL commands (INSERTs,
UPDATEs, SELECTs) from a client application to a database that happens
to be sitting on a server somewhere that I can only reach via HTTP
(https actually), due to firewall restrictions. I don't want to have
to modify my application, but note that it has the ability to use any
ODBC, ADO/OLEDB or a direct SQL native driver, depending on the
connection string supplied. I certainly don't want to have to care that
requests and results are being transmitted in XML SOAP format (or
whatever).
>From the various connection strings I've seen around, and the little
information I've seen regarding HTTP requests to SQL server, it
certainly isn't possible with the standard drivers etc. that Microsoft
supply, but if so, surely there's a demand for such a thing?
In article <1163482089.627876.121280@.h54g2000cwb.googlegroups .com>, wizofaus@.hotmail.com wrote:
>Does there exist an ODBC or OLEDB/ADODB driver for talking to SQL
>server over HTTP/port 80?
>In other words, I want to be able to issue SQL commands (INSERTs,
>UPDATEs, SELECTs) from a client application to a database that happens
>to be sitting on a server somewhere that I can only reach via HTTP
>(https actually), due to firewall restrictions. I don't want to have
>to modify my application, but note that it has the ability to use any
>ODBC, ADO/OLEDB or a direct SQL native driver, depending on the
>connection string supplied. I certainly don't want to have to care that
>requests and results are being transmitted in XML SOAP format (or
>whatever).
>information I've seen regarding HTTP requests to SQL server, it
>certainly isn't possible with the standard drivers etc. that Microsoft
>supply, but if so, surely there's a demand for such a thing?
>
You're not limited to http, you're limited to port 80
Just set SQL Server to listen on port 80, instead of the traditional 1433.
It sounds like this is at least partly internet accesible.
Be REAL careful about exposed SQL Servers on the net. There are a lot of
exploits...
|||Brian Bunin wrote:
> In article <1163482089.627876.121280@.h54g2000cwb.googlegroups .com>, wizofaus@.hotmail.com wrote:
> You're not limited to http, you're limited to port 80
> Just set SQL Server to listen on port 80, instead of the traditional 1433.
> It sounds like this is at least partly internet accesible.
No, because the firewall explicitly examines the packets to ensure they
are HTTP(S) packets only.
And actually I'd expect to use port 443.

> Be REAL careful about exposed SQL Servers on the net. There are a lot of
> exploits...
Well of course, but as it is the machine has open Terminal Service
access (of course you need a username and password ), so it's not
really less secure exposing another port for direct SQL server access.
The database doesn't hold particularly critical or sensitive data
anyway.
But SQL server *does* have (or at least, can support, along with IIS) a
web based interface...so why shouldn't I be able to talk to it without
caring that it is web-based or otherwise?
|||wizofaus@.hotmail.com wrote:
> Does there exist an ODBC or OLEDB/ADODB driver for talking to SQL
> server over HTTP/port 80?
> In other words, I want to be able to issue SQL commands (INSERTs,
> UPDATEs, SELECTs) from a client application to a database that happens
> to be sitting on a server somewhere that I can only reach via HTTP
> (https actually), due to firewall restrictions. I don't want to have
> to modify my application, but note that it has the ability to use any
> ODBC, ADO/OLEDB or a direct SQL native driver, depending on the
> connection string supplied. I certainly don't want to have to care that
> requests and results are being transmitted in XML SOAP format (or
> whatever).
> information I've seen regarding HTTP requests to SQL server, it
> certainly isn't possible with the standard drivers etc. that Microsoft
> supply, but if so, surely there's a demand for such a thing?
>
Have you considered creating some web methods?
That would allow you to consume and utilize SQL data over port 80, but
not open up your entire range of functions.
The Texeme Construct
http://you-read-it-here-first.com

ODBC/OLEDB support for HTTP-based comms to SQL server?

Does there exist an ODBC or OLEDB/ADODB driver for talking to SQL
server over HTTP/port 80?
In other words, I want to be able to issue SQL commands (INSERTs,
UPDATEs, SELECTs) from a client application to a database that happens
to be sitting on a server somewhere that I can only reach via HTTP
(https actually), due to firewall restrictions. I don't want to have
to modify my application, but note that it has the ability to use any
ODBC, ADO/OLEDB or a direct SQL native driver, depending on the
connection string supplied. I certainly don't want to have to care that
requests and results are being transmitted in XML SOAP format (or
whatever).
>From the various connection strings I've seen around, and the little
information I've seen regarding HTTP requests to SQL server, it
certainly isn't possible with the standard drivers etc. that Microsoft
supply, but if so, surely there's a demand for such a thing?In article <1163482089.627876.121280@.h54g2000cwb.googlegroups.com>, wizofaus@.hotmail.com wro
te:
>Does there exist an ODBC or OLEDB/ADODB driver for talking to SQL
>server over HTTP/port 80?
>In other words, I want to be able to issue SQL commands (INSERTs,
>UPDATEs, SELECTs) from a client application to a database that happens
>to be sitting on a server somewhere that I can only reach via HTTP
>(https actually), due to firewall restrictions. I don't want to have
>to modify my application, but note that it has the ability to use any
>ODBC, ADO/OLEDB or a direct SQL native driver, depending on the
>connection string supplied. I certainly don't want to have to care that
>requests and results are being transmitted in XML SOAP format (or
>whatever).
>information I've seen regarding HTTP requests to SQL server, it
>certainly isn't possible with the standard drivers etc. that Microsoft
>supply, but if so, surely there's a demand for such a thing?
>
You're not limited to http, you're limited to port 80
Just set SQL Server to listen on port 80, instead of the traditional 1433.
It sounds like this is at least partly internet accesible.
Be REAL careful about exposed SQL Servers on the net. There are a lot of
exploits...|||Brian Bunin wrote:
> In article <1163482089.627876.121280@.h54g2000cwb.googlegroups.com>, wizofa
us@.hotmail.com wrote:
> You're not limited to http, you're limited to port 80
> Just set SQL Server to listen on port 80, instead of the traditional 1433.
> It sounds like this is at least partly internet accesible.
No, because the firewall explicitly examines the packets to ensure they
are HTTP(S) packets only.
And actually I'd expect to use port 443.

> Be REAL careful about exposed SQL Servers on the net. There are a lot of
> exploits...
Well of course, but as it is the machine has open Terminal Service
access (of course you need a username and password ), so it's not
really less secure exposing another port for direct SQL server access.
The database doesn't hold particularly critical or sensitive data
anyway.
But SQL server *does* have (or at least, can support, along with IIS) a
web based interface...so why shouldn't I be able to talk to it without
caring that it is web-based or otherwise?|||wizofaus@.hotmail.com wrote:
> Does there exist an ODBC or OLEDB/ADODB driver for talking to SQL
> server over HTTP/port 80?
> In other words, I want to be able to issue SQL commands (INSERTs,
> UPDATEs, SELECTs) from a client application to a database that happens
> to be sitting on a server somewhere that I can only reach via HTTP
> (https actually), due to firewall restrictions. I don't want to have
> to modify my application, but note that it has the ability to use any
> ODBC, ADO/OLEDB or a direct SQL native driver, depending on the
> connection string supplied. I certainly don't want to have to care that
> requests and results are being transmitted in XML SOAP format (or
> whatever).
> information I've seen regarding HTTP requests to SQL server, it
> certainly isn't possible with the standard drivers etc. that Microsoft
> supply, but if so, surely there's a demand for such a thing?
>
Have you considered creating some web methods?
That would allow you to consume and utilize SQL data over port 80, but
not open up your entire range of functions.
The Texeme Construct
http://you-read-it-here-first.com

odbc timeout

Hi Ralf
I am not sure why you need to create a new ODBC connection if this
previously existed? If this did not previously exist then you can not say fo
r
certain it is the NIC that is causing this, therefore check to see if you ca
n
ping the server and/or connect via osql, check that the firewall is not
blocking any port being used. Other things to look out for would be faulty
cabling, a problem with a hub or switch, out-of-date drivers.
John
"Ralf Temme" wrote:

> Hallo,
> we have to installed a new nic on a w2k-server with sql-server2000. The
> proberties TCP/IP are the same like on the old nic. SQL-Connection are oka
y,
> but not the odbc-connection! During the configuratin of the odbc-connectio
n
> on the client we recieve an timeout error. 1.-3. or 4. try are succesful.
But
> than timeout. Nameresolution seems okay. We have no error massage or id. O
nly
> timeout, connection failed!
> What′s the reason for this? Only a new network-card!
> Thanks for help!Hallo,
we have to installed a new nic on a w2k-server with sql-server2000. The
proberties TCP/IP are the same like on the old nic. SQL-Connection are okay,
but not the odbc-connection! During the configuratin of the odbc-connection
on the client we recieve an timeout error. 1.-3. or 4. try are succesful. Bu
t
than timeout. Nameresolution seems okay. We have no error massage or id. Onl
y
timeout, connection failed!
What′s the reason for this? Only a new network-card!
Thanks for help!|||Hi Ralf
I am not sure why you need to create a new ODBC connection if this
previously existed? If this did not previously exist then you can not say fo
r
certain it is the NIC that is causing this, therefore check to see if you ca
n
ping the server and/or connect via osql, check that the firewall is not
blocking any port being used. Other things to look out for would be faulty
cabling, a problem with a hub or switch, out-of-date drivers.
John
"Ralf Temme" wrote:

> Hallo,
> we have to installed a new nic on a w2k-server with sql-server2000. The
> proberties TCP/IP are the same like on the old nic. SQL-Connection are oka
y,
> but not the odbc-connection! During the configuratin of the odbc-connectio
n
> on the client we recieve an timeout error. 1.-3. or 4. try are succesful.
But
> than timeout. Nameresolution seems okay. We have no error massage or id. O
nly
> timeout, connection failed!
> What′s the reason for this? Only a new network-card!
> Thanks for help!|||Hi John,
we create a new odbc connection only for testing. The error is the same like
the old one. We have applications as sql-clients, works normaly. So I′m sur
e
network connection is okay. One application needs the odbc connection. These
one failed with timeout error. Try to connect passed 3-4 times, than
timeout. After a few seconds I can start again: the same (passed 3-4 times,
than timeout). ODBCPING passed. Ping passed. Firewall is not activ. MDAC is
new. SP4 for SQL-Server is installed. Driver for the NIC (Intel) is the new.
It seems like an limit of odbc-requests, but I don′t know!
"John Bell" schrieb:
[vbcol=seagreen]
> Hi Ralf
> I am not sure why you need to create a new ODBC connection if this
> previously existed? If this did not previously exist then you can not say
for
> certain it is the NIC that is causing this, therefore check to see if you
can
> ping the server and/or connect via osql, check that the firewall is not
> blocking any port being used. Other things to look out for would be faulty
> cabling, a problem with a hub or switch, out-of-date drivers.
> John
> "Ralf Temme" wrote:
>|||Hi Ralf
If there is a limit on your connections then I would expect other systems to
experience problems as well! You could set ODBC tracing on, but I am not sur
e
that it will tell you anything extra. You may also want to try a different
NIC that you know is working. You may also want to try plugging the maching
into the same hub/switch as the server using different cables.
John
"Ralf Temme" wrote:
[vbcol=seagreen]
> Hi John,
> we create a new odbc connection only for testing. The error is the same li
ke
> the old one. We have applications as sql-clients, works normaly. So I′m s
ure
> network connection is okay. One application needs the odbc connection. The
se
> one failed with timeout error. Try to connect passed 3-4 times, than
> timeout. After a few seconds I can start again: the same (passed 3-4 times
,
> than timeout). ODBCPING passed. Ping passed. Firewall is not activ. MDAC i
s
> new. SP4 for SQL-Server is installed. Driver for the NIC (Intel) is the ne
w.
> It seems like an limit of odbc-requests, but I don′t know!
> "John Bell" schrieb:
>|||You say that one app is having problems. What is the MDAC for the app softwa
re?
Is the app using 'generic' odbc or is it writing to the API?
Also, during the set up of the ODBC driver in ODBC Administrator,t here is a
'test connection' option. When you do that test does it fail?
"John Bell" wrote:
[vbcol=seagreen]
> Hi Ralf
> If there is a limit on your connections then I would expect other systems
to
> experience problems as well! You could set ODBC tracing on, but I am not s
ure
> that it will tell you anything extra. You may also want to try a different
> NIC that you know is working. You may also want to try plugging the machin
g
> into the same hub/switch as the server using different cables.
> John
>
> "Ralf Temme" wrote:
>|||Hi John,
we create a new odbc connection only for testing. The error is the same like
the old one. We have applications as sql-clients, works normaly. So I′m sur
e
network connection is okay. One application needs the odbc connection. These
one failed with timeout error. Try to connect passed 3-4 times, than
timeout. After a few seconds I can start again: the same (passed 3-4 times,
than timeout). ODBCPING passed. Ping passed. Firewall is not activ. MDAC is
new. SP4 for SQL-Server is installed. Driver for the NIC (Intel) is the new.
It seems like an limit of odbc-requests, but I don′t know!
"John Bell" schrieb:
[vbcol=seagreen]
> Hi Ralf
> I am not sure why you need to create a new ODBC connection if this
> previously existed? If this did not previously exist then you can not say
for
> certain it is the NIC that is causing this, therefore check to see if you
can
> ping the server and/or connect via osql, check that the firewall is not
> blocking any port being used. Other things to look out for would be faulty
> cabling, a problem with a hub or switch, out-of-date drivers.
> John
> "Ralf Temme" wrote:
>|||Hi Ralf
If there is a limit on your connections then I would expect other systems to
experience problems as well! You could set ODBC tracing on, but I am not sur
e
that it will tell you anything extra. You may also want to try a different
NIC that you know is working. You may also want to try plugging the maching
into the same hub/switch as the server using different cables.
John
"Ralf Temme" wrote:
[vbcol=seagreen]
> Hi John,
> we create a new odbc connection only for testing. The error is the same li
ke
> the old one. We have applications as sql-clients, works normaly. So I′m s
ure
> network connection is okay. One application needs the odbc connection. The
se
> one failed with timeout error. Try to connect passed 3-4 times, than
> timeout. After a few seconds I can start again: the same (passed 3-4 times
,
> than timeout). ODBCPING passed. Ping passed. Firewall is not activ. MDAC i
s
> new. SP4 for SQL-Server is installed. Driver for the NIC (Intel) is the ne
w.
> It seems like an limit of odbc-requests, but I don′t know!
> "John Bell" schrieb:
>|||You say that one app is having problems. What is the MDAC for the app softwa
re?
Is the app using 'generic' odbc or is it writing to the API?
Also, during the set up of the ODBC driver in ODBC Administrator,t here is a
'test connection' option. When you do that test does it fail?
"John Bell" wrote:
[vbcol=seagreen]
> Hi Ralf
> If there is a limit on your connections then I would expect other systems
to
> experience problems as well! You could set ODBC tracing on, but I am not s
ure
> that it will tell you anything extra. You may also want to try a different
> NIC that you know is working. You may also want to try plugging the machin
g
> into the same hub/switch as the server using different cables.
> John
>
> "Ralf Temme" wrote:
>

odbc sql server does not exist or access denied

I just installed SQL 2005 on a backup/test server. When I connected with ODBC to the new server I lost all of my ODBC connections, even to the working server (SQL 2000). I did a full repair on XP and got the ODBC to connect. Why would connecting to SQL 2005 cause my ODBC to crash ?. I tried using SQL Native as well, with no joy to either server. My ODBC isn't working again. The problem began as being intermittent, i.e. connected one minute, lost connection the next. Now it's permanently disconnected and I'm not even sure the reinstall was a solution.

Take a look at - http://support.microsoft.com/kb/328306

Hope this helps

|||Also got the error from another machine "does not allow remote connections" when connecting to ODBC.

The fix was to ensure that SQL Server Surface Area Configuration (via Start / etc) , Remote Connections set to "Using both TCP/IP and named pipes" (which was already default in my instance), and instead of using the name of the server in the ODBC drop-down list, use the servier IP, i.e. 10.0.0.XXX.|||

Is your issue resolved? If so, please mark your question anwserred.

If you are able to connect using IP address, but not with machine name, most likely you have a DNS problem on your network.

ODBC issue!!!

Im trying to run a very simple script on an index that doesnt exist.

Drop Index BLAH;

Create Index BLAH;

When I run this through an ODBC Connection it fails on the drop since it doesnt exist and STOPS running the script. Im hoping this is a simple setting on my part where if it errors on something as simple as a index to be dropped does not exist then it will continue to the next line in the script

Thanks

Scott

What about first checking in your script if the index you want to drop already exists ?

IF Object_ID('SomeIndexName') IS NOT NULL
DROP INDEX BLAH

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||I can do that butthe amount of modifications that would require would be huge. I was hoping there was an easier way.