Showing posts with label book. Show all posts
Showing posts with label book. Show all posts

Friday, March 9, 2012

How to set rights in E.Manager Since it is a open book..

Hi,

For working with linked servers , Mr. Hills had replied like , one can
not see the login rights etc if the particular user is not in the
admin role in the Enter prise manager.

Since the E.Manager is a open book so that any one can access any
database , Do you explain me When the sql server E.manager ks the
user's login and password .

With thanks

RAGHUWhen you register a server in EM you specify an authentication mode.

If you choose Windows Authentication then the login information is taken
from your Windows domain login - you will have access only to the databases
to which your login has been granted permissions.

If you choose SQL Server Authentication then you can opt either to save the
login name and password in the registry or to prompt for a login name each
time you try to connect to the server in EM. Your level of access is
determined by the SQL Server login name supplied.

For maximum security use Windows Authentication or set the option to prompt
for a login name each time you connect. If you choose Windows Authentication
then also password protect your screen saver so that your PC is secure when
you are away.

Does that answer your question?

--
David Portas
----
Please reply only to the newsgroup
--

Sunday, February 19, 2012

How to send notification to .aspx page...

... as far as I understand, I need to create a custom HTTP protocol. Where do get an example of this? Shyam's book has an example of creating custom protocol that is not HTTP based. There are few remarks on HTTP custom protocol in Chapter 10, but those are not very helpful.

The scenario it is used for is as follows: ASP.NET messenger (an .aspx page) writes messages into SQL server table. The page needs to get notified as soon as new entry appears in the table (from another instance of messenger), so that the first instance of messenger would be able to get new message from the table. Is this appropriate usage of notification services? If not, can you suggest alternative ways to write ASP.NET messenger?

Thank you in advance.

Is this a kinda IM application ? If so NS is not a right choice for Real Time Communication I would prefer to explore RTC (Real Time CommunicationI API with MS Live Communication Server. These two works well for any IM/Messaging related application.

If you mention ur requirements in detail (what do u mean by message etc) i will be more clear... thanks

--Satyen

|||

Query Notifications may be a better technology choice for you in this application.

HTH...

Joe

How to send notification to .aspx page...

... as far as I understand, I need to create a custom HTTP protocol. Where do get an example of this? Shyam's book has an example of creating custom protocol that is not HTTP based. There are few remarks on HTTP custom protocol in Chapter 10, but those are not very helpful.

The scenario it is used for is as follows: ASP.NET messenger (an .aspx page) writes messages into SQL server table. The page needs to get notified as soon as new entry appears in the table (from another instance of messenger), so that the first instance of messenger would be able to get new message from the table. Is this appropriate usage of notification services? If not, can you suggest alternative ways to write ASP.NET messenger?

Thank you in advance.

Is this a kinda IM application ? If so NS is not a right choice for Real Time Communication I would prefer to explore RTC (Real Time CommunicationI API with MS Live Communication Server. These two works well for any IM/Messaging related application.

If you mention ur requirements in detail (what do u mean by message etc) i will be more clear... thanks

--Satyen

|||

Query Notifications may be a better technology choice for you in this application.

HTH...

Joe

How to send notification to .aspx page...

... as far as I understand, I need to create a custom HTTP protocol. Where do get an example of this? Shyam's book has an example of creating custom protocol that is not HTTP based. There are few remarks on HTTP custom protocol in Chapter 10, but those are not very helpful.

The scenario it is used for is as follows: ASP.NET messenger (an .aspx page) writes messages into SQL server table. The page needs to get notified as soon as new entry appears in the table (from another instance of messenger), so that the first instance of messenger would be able to get new message from the table. Is this appropriate usage of notification services? If not, can you suggest alternative ways to write ASP.NET messenger?

Thank you in advance.

Is this a kinda IM application ? If so NS is not a right choice for Real Time Communication I would prefer to explore RTC (Real Time CommunicationI API with MS Live Communication Server. These two works well for any IM/Messaging related application.

If you mention ur requirements in detail (what do u mean by message etc) i will be more clear... thanks

--Satyen

|||

Query Notifications may be a better technology choice for you in this application.

HTH...

Joe