Showing posts with label posting. Show all posts
Showing posts with label posting. Show all posts

Monday, March 12, 2012

insisting on a password policy for sql

Hi
SQL Server 2005 introduces this functionality.
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andre Gibson" <AndreGibson@.discussions.microsoft.com> wrote in message
news:8B9326C5-CF63-4609-A84D-4A596363A8EF@.microsoft.com...
> Is it possible to force users with sql accounts to use secure passwords
> say
> 6 plus characters long with numbers and letters. Is it also possible to
> have
> sql insist that the passwords be changed every X days.
> I am of course talking about when sql server 2000 uses sql authentication.
> Please advise
> AndreThe short answer for SQL 2000 is No.
A much longer answer is that one could 'roll their own' and create some
overly complex custom functionality that most likely would still be
incomplete and fraught with problems.
Waiting for SQL 2005 -and lobbying for its' adoption, is the answer.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Andre Gibson" <AndreGibson@.discussions.microsoft.com> wrote in message
news:8B9326C5-CF63-4609-A84D-4A596363A8EF@.microsoft.com...
> Is it possible to force users with sql accounts to use secure passwords
> say
> 6 plus characters long with numbers and letters. Is it also possible to
> have
> sql insist that the passwords be changed every X days.
> I am of course talking about when sql server 2000 uses sql authentication.
> Please advise
> Andre|||Is it possible to force users with sql accounts to use secure passwords say
6 plus characters long with numbers and letters. Is it also possible to have
sql insist that the passwords be changed every X days.
I am of course talking about when sql server 2000 uses sql authentication.
Please advise
Andre|||Hi
SQL Server 2005 introduces this functionality.
Regards
--
Mike
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andre Gibson" <AndreGibson@.discussions.microsoft.com> wrote in message
news:8B9326C5-CF63-4609-A84D-4A596363A8EF@.microsoft.com...
> Is it possible to force users with sql accounts to use secure passwords
> say
> 6 plus characters long with numbers and letters. Is it also possible to
> have
> sql insist that the passwords be changed every X days.
> I am of course talking about when sql server 2000 uses sql authentication.
> Please advise
> Andre|||The short answer for SQL 2000 is No.
A much longer answer is that one could 'roll their own' and create some
overly complex custom functionality that most likely would still be
incomplete and fraught with problems.
Waiting for SQL 2005 -and lobbying for its' adoption, is the answer.
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
"Andre Gibson" <AndreGibson@.discussions.microsoft.com> wrote in message
news:8B9326C5-CF63-4609-A84D-4A596363A8EF@.microsoft.com...
> Is it possible to force users with sql accounts to use secure passwords
> say
> 6 plus characters long with numbers and letters. Is it also possible to
> have
> sql insist that the passwords be changed every X days.
> I am of course talking about when sql server 2000 uses sql authentication.
> Please advise
> Andre

Sunday, February 19, 2012

Inserting records and displaying them

Before I start driving myself nuts, I'd like to make sure my approach is correct.

I want to create a simple job posting board.
I have a text boxes for company name, email, job title, and job description, and a submit button.
I created a table in my database called "JobPostings", with columns called "CoName", "CoEmail", "JobTitle", and "JobDesc"

When someone fills out the fields and clicks submit, it will insert the new records.

So,
1. Is this the correct approach so far?

2. What is the best way to display the job listings? A grid view?

3. At submit time, how can I include that day's date?

4. How can I get the records in the database to delete after 90 days?

Thanks.

1. If it did what you want, it's correct to youSmile

2. You can try SqlDataSource+GridView, see

3. You can add a datetime column (e.g. CreateDate) to the table, whose default value is getdate() so that when a new record being inserted you don't need to specify date for the column:

ALTER TABLE mytable ADD CreateDate DATETIME DEFAULT GetDate()

4. You can use such command to delete records older than 90 days:

DELETE FROM mytable WHERE DATEDIFF(d,CreateDate,GETDATE())>90