Peer2Peer Transactional Replication

Hi,
Anyone know why the view/ store procedure does not replicate from ServerA to
ServerB?
Thanks,
Kenny
They will be in place if you deploy your subscribers from a backup. If you
create the subscription manually you will need to create them on each node
as well.
Note that if you create a new view or stored procedure they will not be
replicated to each node.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kenny" <Kenny@.discussions.microsoft.com> wrote in message
news:5CA78A4E-78B4-488C-BF83-2D4B88A1FCA9@.microsoft.com...
> Hi,
> Anyone know why the view/ store procedure does not replicate from ServerA
> to
> ServerB?
> Thanks,
> Kenny

pattern matching

hullo all,

well i need to read pages online using webclient or httmpweb classes
and store them in string builder to perform further string operations.

any idea regarding its code

This seems more like an application issue. You might try posting on one of the pertinent .NET forums.|||

ummm well ur qoute proves true..

thanks

password storage

hai all!
i am going to store my user details to login from vb.net in a user table in sql.i would like to disguise the password column with dots or stars.how do i do that?kindly help.its urgent.i also need to compare the password right.so it should be readable by the program

Quote:

Originally Posted by pangsans

hai all!
i am going to store my user details to login from vb.net in a user table in sql.i would like to disguise the password column with dots or stars.how do i do that?kindly help.its urgent.i also need to compare the password right.so it should be readable by the program

i doubt if you can revert back to the original string from "dots or stars", what you could is to use an encrypting function...you may create your own or find one on the net|||

Quote:

Originally Posted by ck9663

i doubt if you can revert back to the original string from "dots or stars", what you could is to use an encrypting function...you may create your own or find one on the net

thanks yaar
give me some more info yaar|||That would depend on how you want to encrypt it. one way or 2 way?
and syntax will differ from language to language :)
cheers

Password in SQL

Hi,
Is there a way I can store password in SQL table as
encrypted using SQL table defintion instead of writing code
to do encrypt and decrypt?
Thanks.
Hi
Not with SQL Server 2000. SQL Server 2005 supports this.
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/
"dbc user" <anonymous@.discussions.microsoft.com> wrote in message
news:07b101c5191b$0ee24b50$a601280a@.phx.gbl...
> Hi,
> Is there a way I can store password in SQL table as
> encrypted using SQL table defintion instead of writing code
> to do encrypt and decrypt?
> Thanks.
|||Ok. Thanks
>--Original Message--
>Hi
>Not with SQL Server 2000. SQL Server 2005 supports this.
>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/
>"dbc user" <anonymous@.discussions.microsoft.com> wrote in
message
>news:07b101c5191b$0ee24b50$a601280a@.phx.gbl...
>
>.
>

Password Field in SQL Server

If i would like to have the field to store password(data, ****), what type
of field in sql server?
is it good to select binary?Storing passwords is an inherently insecure practice that would
probably fall foul of a security audit (a good audit anyway). If you
must roll your own security then store a salted, secure hash of the
password. For that BINARY is the obvious choice.
--
David Portas
SQL Server MVP
--|||Implement your own en/decryptring methody in your middle tier to
accomplish this.
HTH, jens Suessmeyer.

Password Field in SQL Server

If i would like to have the field to store password(data, ****), what type
of field in sql server?
is it good to select binary?
Storing passwords is an inherently insecure practice that would
probably fall foul of a security audit (a good audit anyway). If you
must roll your own security then store a salted, secure hash of the
password. For that BINARY is the obvious choice.
David Portas
SQL Server MVP
|||Implement your own en/decryptring methody in your middle tier to
accomplish this.
HTH, jens Suessmeyer.

Password Field in SQL Server

If i would like to have the field to store password(data, ****), what type
of field in sql server?
is it good to select binary?Storing passwords is an inherently insecure practice that would
probably fall foul of a security audit (a good audit anyway). If you
must roll your own security then store a salted, secure hash of the
password. For that BINARY is the obvious choice.
David Portas
SQL Server MVP
--|||Implement your own en/decryptring methody in your middle tier to
accomplish this.
HTH, jens Suessmeyer.

Password field (very important)

A collegue from me used the MySQL database before (I haven't done this before). He asked me, if it is possible to store a MD5 hash in a cell.

He telled me that MySQL has got a special function wich computes the hash value. Can someone help me?

Thanks for help

This isn't a MySQL forum so you're fairly unlikely to get an answer here.

-Jamie

|||Sorry for my bad writing. I've forgotten to ask, whether it is possible to make this with the MSSQL.|||

I don't know if its possible in SQL Server but its possible to do it in SSIS (this is a SSIS forum after all).

Donald Farmer's book has a chapter telling you how to generate MC5 values in SSIS. Search for it on Amazon.

-Jamie

password encryption

I have an Access .adp application and I need to store the passwords encrypted. I see that there are unsupported functions pwdencrypt() and pwdcompare() in SQL server 2K.
Are there any other functions or methods in SQL Server 2000 that could be called that would provide this capability?Are there any other functions or methods in SQL Server 2000 that could be called that would provide this capability?

SQL Server 2000 encryption is pretty weak. 2005 is supposed to address this. In the meantime, you might consider this link:

http://www.sqlservercentral.com/columnists/mcoles/freeencryption.asp

(you may have to register, but registration is free).

Alternatively, you could use the Micrsoft Crypto API (capicom.dll) or the .Net Encryption utilities (don't have more specific references on these).

Regards,

hmscott

Passing table name as parameter in stored procedure

Hey guys,
Im trying to create a store procedure that will perform certain duties on a
given table. The table name will be passed as a parameter.
The problem is I am not allowed to use the parameter as a tablename, so the
following queries are rejected:
SELECT #temp.[id] as SForceID, @.Table.[id] as OppID INTO #Temp2 FROM @.Table
LEFT OUTER JOIN #Temp ON #Temp.[id] = @.Table.[id]
DELETE FROM @.Table WHERE [id] IN (SELECT OppID FROM #Temp2 WHERE SForceID IS
NULL)
How do I achieve this? Is it doable? Is it perhaps a limitation?
Thank you in advance.Juan,
It is doable using dynamic sql but you may need to think about the
design.These are well discussed in the below article by Erland Sommarskog:
The Curse and Blessings of Dynamic SQL
http://www.algonet.se/~sommar/dynamic_sql.html#Dyn_table
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Juan Romero" <juanja01@.optonline.net> wrote in message
news:%23M9Mi2iUDHA.1916@.TK2MSFTNGP12.phx.gbl...
> Hey guys,
> Im trying to create a store procedure that will perform certain duties on
a
> given table. The table name will be passed as a parameter.
> The problem is I am not allowed to use the parameter as a tablename, so
the
> following queries are rejected:
> SELECT #temp.[id] as SForceID, @.Table.[id] as OppID INTO #Temp2 FROM
@.Table
> LEFT OUTER JOIN #Temp ON #Temp.[id] = @.Table.[id]
> DELETE FROM @.Table WHERE [id] IN (SELECT OppID FROM #Temp2 WHERE SForceID
IS
> NULL)
> How do I achieve this? Is it doable? Is it perhaps a limitation?
> Thank you in advance.
>