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?

ODBC Link to SQL 2005

I am trying to link table to Access 2003 from SQL 2005
Some tables come across ok but others just have the word deleted in all the
fields
Any ideas?
Maybe these table have a missing primary key or you using a type of field -
such as BIGINT - which is incompatible with Access. Nullable bit value (Bit
field without a default value and that can be set to Null) and some out of
range precision for decimal/currency type can also be troublesome.
You should make a copy of these tables and start removing the fields until
you find the offensive one(s).
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Newbie" <nospam@.nowhere.com> wrote in message
news:eJ1Vr58ZHHA.4856@.TK2MSFTNGP03.phx.gbl...
>I am trying to link table to Access 2003 from SQL 2005
> Some tables come across ok but others just have the word deleted in all
> the fields
> Any ideas?
>
|||Hi, I needed to figure this out too. Evidently, use of bigint (or other
floating) used as a key will not produce an updateable link. In access, you
probably don't want to anyway, but it would be nice to see the data instead
of #Delete splattered all over the screen. My solution: Set up a query
(simple select *), and change the Recordset Type property to Snapshot. Use
this snapshot query as a source to any subsequent work.
"Newbie" wrote:

> I am trying to link table to Access 2003 from SQL 2005
> Some tables come across ok but others just have the word deleted in all the
> fields
> Any ideas?
>
>
|||you just need to use Access DAta Projects
all this linking crap is called 'unnecessary complexity'
"phillips001" <phillips001@.discussions.microsoft.com> wrote in message
news:F1BF9A8D-412E-476A-B164-2AE3CDE0B95B@.microsoft.com...[vbcol=seagreen]
> Hi, I needed to figure this out too. Evidently, use of bigint (or other
> floating) used as a key will not produce an updateable link. In access,
> you
> probably don't want to anyway, but it would be nice to see the data
> instead
> of #Delete splattered all over the screen. My solution: Set up a query
> (simple select *), and change the Recordset Type property to Snapshot.
> Use
> this snapshot query as a source to any subsequent work.
> "Newbie" wrote:
|||Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
"Tom Wickerath" <tom_wickerath@.hotmail.com> wrote in message
news:uVxngNdnHHA.1240@.TK2MSFTNGP04.phx.gbl...
> you just need to use Access DAta Projects
> all this linking crap is called 'unnecessary complexity'
>
> "phillips001" <phillips001@.discussions.microsoft.com> wrote in message
> news:F1BF9A8D-412E-476A-B164-2AE3CDE0B95B@.microsoft.com...
>

ODBC Link to SQL 2005

I am trying to link table to Access 2003 from SQL 2005
Some tables come across ok but others just have the word deleted in all the
fields
Any ideas?Maybe these table have a missing primary key or you using a type of field -
such as BIGINT - which is incompatible with Access. Nullable bit value (Bit
field without a default value and that can be set to Null) and some out of
range precision for decimal/currency type can also be troublesome.
You should make a copy of these tables and start removing the fields until
you find the offensive one(s).
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Newbie" <nospam@.nowhere.com> wrote in message
news:eJ1Vr58ZHHA.4856@.TK2MSFTNGP03.phx.gbl...
>I am trying to link table to Access 2003 from SQL 2005
> Some tables come across ok but others just have the word deleted in all
> the fields
> Any ideas?
>|||Hi, I needed to figure this out too. Evidently, use of bigint (or other
floating) used as a key will not produce an updateable link. In access, you
probably don't want to anyway, but it would be nice to see the data instead
of #Delete splattered all over the screen. My solution: Set up a query
(simple select *), and change the Recordset Type property to Snapshot. Use
this snapshot query as a source to any subsequent work.
"Newbie" wrote:

> I am trying to link table to Access 2003 from SQL 2005
> Some tables come across ok but others just have the word deleted in all th
e
> fields
> Any ideas?
>
>|||you just need to use Access DAta Projects
all this linking crap is called 'unnecessary complexity'
"phillips001" <phillips001@.discussions.microsoft.com> wrote in message
news:F1BF9A8D-412E-476A-B164-2AE3CDE0B95B@.microsoft.com...[vbcol=seagreen]
> Hi, I needed to figure this out too. Evidently, use of bigint (or other
> floating) used as a key will not produce an updateable link. In access,
> you
> probably don't want to anyway, but it would be nice to see the data
> instead
> of #Delete splattered all over the screen. My solution: Set up a query
> (simple select *), and change the Recordset Type property to Snapshot.
> Use
> this snapshot query as a source to any subsequent work.
> "Newbie" wrote:
>|||Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com,www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/e...tributors2.html for contact
info.
"Tom Wickerath" <tom_wickerath@.hotmail.com> wrote in message
news:uVxngNdnHHA.1240@.TK2MSFTNGP04.phx.gbl...
> you just need to use Access DAta Projects
> all this linking crap is called 'unnecessary complexity'
>
> "phillips001" <phillips001@.discussions.microsoft.com> wrote in message
> news:F1BF9A8D-412E-476A-B164-2AE3CDE0B95B@.microsoft.com...
>

ODBC Link to SQL 2005

I am trying to link table to Access 2003 from SQL 2005
Some tables come across ok but others just have the word deleted in all the
fields
Any ideas?
Maybe these table have a missing primary key or you using a type of field -
such as BIGINT - which is incompatible with Access. Nullable bit value (Bit
field without a default value and that can be set to Null) and some out of
range precision for decimal/currency type can also be troublesome.
You should make a copy of these tables and start removing the fields until
you find the offensive one(s).
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Newbie" <nospam@.nowhere.com> wrote in message
news:eJ1Vr58ZHHA.4856@.TK2MSFTNGP03.phx.gbl...
>I am trying to link table to Access 2003 from SQL 2005
> Some tables come across ok but others just have the word deleted in all
> the fields
> Any ideas?
>
|||Hi, I needed to figure this out too. Evidently, use of bigint (or other
floating) used as a key will not produce an updateable link. In access, you
probably don't want to anyway, but it would be nice to see the data instead
of #Delete splattered all over the screen. My solution: Set up a query
(simple select *), and change the Recordset Type property to Snapshot. Use
this snapshot query as a source to any subsequent work.
"Newbie" wrote:

> I am trying to link table to Access 2003 from SQL 2005
> Some tables come across ok but others just have the word deleted in all the
> fields
> Any ideas?
>
>
|||you just need to use Access DAta Projects
all this linking crap is called 'unnecessary complexity'
"phillips001" <phillips001@.discussions.microsoft.com> wrote in message
news:F1BF9A8D-412E-476A-B164-2AE3CDE0B95B@.microsoft.com...[vbcol=seagreen]
> Hi, I needed to figure this out too. Evidently, use of bigint (or other
> floating) used as a key will not produce an updateable link. In access,
> you
> probably don't want to anyway, but it would be nice to see the data
> instead
> of #Delete splattered all over the screen. My solution: Set up a query
> (simple select *), and change the Recordset Type property to Snapshot.
> Use
> this snapshot query as a source to any subsequent work.
> "Newbie" wrote:
|||Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
"Tom Wickerath" <tom_wickerath@.hotmail.com> wrote in message
news:uVxngNdnHHA.1240@.TK2MSFTNGP04.phx.gbl...
> you just need to use Access DAta Projects
> all this linking crap is called 'unnecessary complexity'
>
> "phillips001" <phillips001@.discussions.microsoft.com> wrote in message
> news:F1BF9A8D-412E-476A-B164-2AE3CDE0B95B@.microsoft.com...
>