This has to be a simple question for most of you, so here goes.
My passwords for sa and another login that I created keep resetting.
How can I turn off password expiration in SQL Server 2000?
Thanks!
MB
I have configured a Linked Server with Active Directory (LDAP), working properly.
Now, through this Linked Server, I need information about password expiration date in my AD Domain accounts.
We need to use SQL Server Authentication for some reason and would like to enforce Password Policy with 90-day expiration period. I found "Change password" dialogue appears when I first logged in with the new user, but don't know
(1)what happens when the user failed to change the password before it's expired or
(2)how a user can change his password in advance of the expiration date with no particular server-level permission.
Hello,
I am building a winforms .net 3.5 application which connects to a SQL Server 2005 database with SQL server authentication. Is it possible to access the SQL Server password policy and expiration through the .NET 3.5 framework? I would like add the following functionality to my login form:
Ensure passwords meet policy standard.
Prompt a user to change their password when it is due to expire in 5 days or less.
Thanks in advance.
Numerous articles (e.g., http://www.microsoft.com/sql/techinfo/administration/2000/security/securingsqlserver.asp, even one that I wrote, http://www.dbazine.com/sql/sql-articles/cook12) state that to secure SQL Server, the SQL Server services should not run as Local System. That advice is useful only if making the change is not overly disruptive or is even allowable. My two most recent clients have absolutely rigid password expiration policies that require all account passwords to be changed at regular intervals. Realistically, that makes a compelling case for running as Local System.
View 4 Replies View RelatedHello,
Is there a way to find out many days you have left on the trial period or is there a way to find out when it was created. I get the feeling it will just not work one of these days and I'll have to figure out something on the fly.
Thank in advance
I have a package protected by a password - I am already unhappy that to get it to use the configuration file to change connection strings for the production servers I have had to hardcode the password into the config file - very insecure!
However, the package now deploys correctly to the production server and will run from there OK, but NOT if scheduled as a SQL Server Agent Job. Thus is because however often I edit the command line to include the password after the DECRYPT switch (which it has prompted me for when I click on the command line tab), the Job Step will not retain it.
If I open it up after I have edited it and closed it, the password has disappeared.
I know that if I run dtexec plus the code in the Command Line tab (with the password), the package runs OK.
This is driving me insane!
I have read all the other posts and so I tried replacing the SSIS package step with a CmdExec step and pasting that code into there - then I get an OLEDB error..
The code I use is:
DTEXEC /SQL "ImportRateMonitoringTables" /SERVER servername /DECRYPT password /CONFIGFILE "D:Microsoft SQL ServerSSISDeploymentsRateMonitoringImportTasksDeploymentImportRateMonitoringTables_Production.dtsConfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E
and I get
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x8000FFFF
although the same code executes perfectly from a command prompt.
Please does anyone have any experience with a similar problem and if so, how did you get round it?
Thank you
I tried to install an ALLDATA database which run with SQL Server 2005 express edition. The data base fails to install becase of the following code that come up which is related to AS password requirement. The error that come up is:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
The sa password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=28001&EvtType=sqlca%5csqlcax.cpp%40SAPasswordPolicyCheck%40SAPasswordPolicyCheck%40x6d61
------------------------------
BUTTONS:
&Retry
Cancel
------------------------------
I am trying to install this database in a network server operating under Windows Server 2003 R2 with SP2. If anyone knows how to solve this problem, please let me.
Thanks,
Amilcar
I am having a pretty major problem with my SQL server. Everytime that I try to query the database I receive a timeout expired error. Even trying to open the query anylyzer, it presents me with that error. We have a we based ISP management solution and it cannot access the SQL either. This was an all the sudden problem and I have ran the performance monitor to try and look at the statistics. Everything seems like it is checking out. I even tried increasing the Timeout up to 20 seconds and it still will not function properly. Any suggestions?
View 1 Replies View Relatedhi,
here i am using .mdf file as database for my project. i want this .mdf file should be expired or become read only after 365 days exactly. how can i achieve this?
One can never consent to creep,when one feels an impulse to soar
RAMMOHAN
Is there a document that lists the expiration dates of the CTP releases? We've a test box still on CTP15 and I was wondering when the CTP will stop working.
View 4 Replies View Related Hi,
Description: In the past I had an issue with the replication that suddenly became expired (no reason at all) and I had to re-do the whole thing from scratch. This is a transactional replication (SQL2.5K -> SQL2.5K) and the subscriber is used as warehouse where applications also inserting data (with neg. seed values for the PKs). This means applying the snapshot from the publisher is not applicable because there are data which will be lost from subscriber.
Question: Since the applying snapshot is not an option for reinitializing the subscription (initially was created without snapshot - from the backup and restore is not applicable at this stage) I need to find implementation way for two things:
1. I need subscription never get marked as expired (I did disable job "Expired subscription clean up" but still the replication can be marked as expired from the "Distribution clean up" job which I am not suppose to disable - this has different function as well - cleaning up the delivered transactions)
2. Safely dropping articles from the publication without applying snapshot to the subscriber (see reason above - num.1). If you force to drop the articles, does this mean that the subscription will be marked as expired after period of time? (This again will lead to problems as above).
Please, give me your opinion and/or best practices how to solve these problems. Other than that I am very happy with the improvements in the replication domain in SQL 2005.
Regards,
Zlatko
I have two tables totally unrelated but give the same information, the difference is the duration. I need to create a stored procedure that will give the recent issue dates only, accept if they have already expired. I'm not exactly sure how to do that. We only want the employees to see the current issue date as long as the exclusion has not expired. Can anyone help please. What needs to happen is that the employees need to see only the exclusions that have expired which is based on the Expiration Date.
Code Block
ALTER PROCEDURE [dbo].[SrchIssueDateLstNm_RecntIssueDte]
@StartIssueDate datetime = null,
@EndIssueDate datetime = null,
@Enter_LastName nvarchar(10) = null
AS
SELECT [dbo].[30 Day exclusion].[First Name], [dbo].[30 Day exclusion].[Last Name], [dbo].[30 Day exclusion].[Issue Date],
[dbo].[Extended Exclusions].[First Name], [dbo].[Extended Exclusions].[Last Name], [dbo].[Extended Exclusions].[Issue Date]
FROM [dbo].[30 Day exclusion]
INNER
JOIN [dbo].[Extended Exclusions]
ON [dbo].[Extended Exclusions].[ID] = [dbo].[30 Day exclusion].[id]
WHERE (@StartIssueDate is null or [Issue Date] >= @StartIssueDate)
AND (@EndIssueDate is null or [Issue Date] <= @EndIssueDate)
AND (@Enter_LastName is null or [Last Name] = @Enter_LastName)
ORDER BY [Last Name]
Setup:
SQL Server 2005 -> Merge pull subscription via HTTPS -> public retention
period is 7 days
Question:
If for some reason I don't synzhronize in 7 days (lets say the Internet is
down for whatever reason), can I reinitialize the subscription on day 9 and
still upload changes to the publisher or not?
I'm guessing the latter based on this:
http://technet.microsoft.com/en-us/library/ms152558.aspx
I have a question on how the retain parameter works for Backups. If I have a nightly full backup for a database and have retain = 10, does that mean on the 11th day the very first backup will be purged? Will the 11th backup attempt to take up some of the space that was occupied by that first backup? It seems that the 11th backup would be too large for the space that the first backup was taking up. I am fairly new to backups with SQL Server and want to ensure I am setting this up properly. Our goal is to keep backups for 10 days only.
View 1 Replies View RelatedI have a table containing several date fields in which certain events happened, and I need to be able to find the expiration date for renewal. The expiration dates are at the end of the 6th, 12th, or 24th month after the event occurred, depending on the event.
Is there a way to return in a query the last day of month x following a date field? For instance, if the date '3/12/2006' is stored in the field for a 12-month expiration, I need to return '3/31/2007'.
Any ideas?
Hi There
This may seem like a stupid question but i am trying to get the hang of the new security model.
I have not really heard anything mentioned about certficate expiration date when it comes to creating certificates for keys or service broker endpoints etc.
We have created certificates for keys and service broker endpoints, now what exactly happens when the expiration date, by default 1 year i think is reached, will we no longer be able to decrypt encrypted data and will the service broker endpoints stop working etc ?
Or is this expiration date when the certificate can no longer be used to create security objects ? And all security objects already created with this certificate will always work ?
In other words is there ever danger that keys and endpoints or basically any object referrencing this certificate will just suddenly stop working one day, or will all objects work indefinately regardless of an certificate/objects expiration date ?
Thanx
We are getting the following error message sporadically:
Network error code 0x2746 occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total 6108 ms, enqueued 1 ms, network writes 1 ms, network reads 6108 ms, establishing SSL 6107 ms, negotiating SSPI 0 ms, validating login 0 ms. [CLIENT: #.#.#.#]
We are seeing this message because we enabled some DBCC trace flags to try and figure out why our clients are having their connections terminated to the SQL 2005 (x64) server we have in production. It appears that the establishment of SSL is taking a very long time according to the log entry. What is using SSL? I'm assuming it is trying to communicate with one of my domain controllers and I'd like to know what perfmon counters i should watch to see what's going on. Is it making an LDAPS connection or kerberos? Or native ntlm?
We've already updated the NIC drivers/firmware and disabled the TcpChimney setting mentioned in the KB articles, but nothing so far has had an effect. I'm now trying to figure out if my DC is overloaded but don't know what counters to look at.
Thanks
Steve
First question: I have sql server 2005 enterprise eval edition installed. is there a query, command or tool can tell me the exact expiration date? I understand it is 180 day but I still want some way to query the exact date.
Second question: does sql server log any warning message before eval expires?
I have had SQL2005 on a server for a very short period of time. Today I found that I am not able to execute an SSIS package in debug. It give me an error stating that the evaluation period has expired for data transformation services. I went to check the version by querying, but nothing happens when I click on the Server Management Studio link.
Has anyone seen this before or how long the trial version should last?
Does anyone know what version may have been installed on my server?
Thanks,
I have an internal Project Management and Scheduling app that I wrote internally for my company. It was written to use MySQL running on a Debian server, but I am going to move it to SQL Server 2000 and integrate it with our Accounting software. The part I am having trouble with is the user login portion. I previously used this:
PHP Code:
$sql = "SELECT * FROM users WHERE username = "$username" AND user_password = password("$password")";
Apparently the password() function is not available when accessing SQL Server via ODBC. Is there an equivalent function I could use isntead so the passwords arent plaintext in the database? I only have 15 people using the system so a blank pwd reset wouldn't be too much trouble.
Is there any way I can check the remaining time before I must upgrade
an SQL Server 2000 Evaluation Edition? I thought I had made a note about
which day it was.
Can I rely upon the file date for uninstallation file in Programs/etc ?
I would like to filter records with in effective date and expiration date; If there is no record within that range, then check for grace period records ( effective date -30 days and expiration date + 90 days)
Below is the detailed script for sample data...
declare @tab table ( sno int identity, name varchar(100), EFFECTIVE_DATE date, EXPIRATION_DATE date)
insert into @tab (name, EFFECTIVE_DATE , EXPIRATION_DATE )
SELECT 'chandu', GETDATE(), NULL union all
SELECT 'chandu', '2014-02-11 00:00:00' , '2014-03-20 00:00:00' union all
SELECT 'AAA', '2014-01-11 00:00:00' , '2014-05-11 00:00:00' union all
[Code] ...
Output:
/*
snonameEFFECTIVE_DATEEXPIRATION_DATE
1chandu2014-03-11NULL
2chandu2014-02-112014-03-20
3AAA2014-01-112014-05-11
4CCC2014-04-09NULL
8DDD2014-03-102014-04-11
*/
Expected output:
snonameEFFECTIVE_DATEEXPIRATION_DATE
1chandu2014-03-11NULL
3AAA2014-01-112014-05-11
4CCC2014-04-09NULL
8DDD2014-03-102014-04-11
Looking for query WITH OUT using GROUP BY clause
Hi,SQL Server 2005 Standard (X64) edition.Have a database which has its log backed up every hour during thenormal business day and each evening a full backup is performed.After two days we would like the the log backups to be automaticallyoverwritten in the backup device [WebAdmin], is this possible?This is the command being used.BACKUP LOG [WebAdmin] TO [WebAdmin]WITH RETAINDAYS = 2,NOFORMAT,NOINIT,NAME = N'WebAdmin',SKIP,NOREWIND,NOUNLOADCurrently the backup device has log backups going back to 18/02/2007which is position number 1 in the device. Basically nothing is beingoverwritten.Thanks in advance.Dave
View 2 Replies View RelatedWe are maintaining a database of drivers, and we are looking for a script or procedure that will automatically notify certain users of the list of drivers who are in need of a recheck or driver's license has expired.
I am new to this , so any help you can give would be greatly appreciated
I have connected to Database using my credentials by checking remember password option. After few days I forgot my password. How can I recover the password as SQL remember it. Is there any way to recover my password instead of resetting it.
View 3 Replies View RelatedI am receiving the following error message when attempting to create a new SQL Authenticated login id.
Password validation failed. The password does not meet the requirements of the password filter DLL. (Microsoft SQL Server, Error: 15119)
I have four servers all running SQL Server 2005 SP2 on Windows 2003 Ent. SP1. Of the four servers, only one received the above error message using the same TSQL below.
CREATE LOGIN TEST_LOGIN WITH PASSWORD = 'pvif9dal' MUST_CHANGE, CHECK_EXPIRATION = ON
All four servers are in the same domain, which if I understand correctly, the password policies are therefore inherited at the OS level by the domain. The password being used is within the password policies of the domain.
Any ideas as to a root cause?
On the login prompt for Report Server, there is a checkbox option to "Remember my Password." I check this, login successfully... but when returning to the Report Server, I am again prompted for the password, although the user name is saved. No matter how many times I do this, the password will not save in IE7. I have tried this on 3 different computers with IE7. In IE 6, I do not even get the checkbox as an option, just the user name/password prompt. In Firefox, the password saves fine. Any ideas what would be causing this?
Thanks,
Brian
I have a complicated question that involves the password policy defined within Windows Server 2003 and how it is used in Microsoft SQL Server 2005. I recently installed windows server 2003 on my development system. I am a person that prefers to develop in the same OS that our application runs in production. After installing 2003, then a Domain administrator added my machine to our corporate domain. Now, I cannot change the local password policy to allow a simple password. I believe this is due to policy inheriting from the domain that the machine belongs to.
This ties back into SQL Server 2005 because installing sql server on a Server 2003 causes SQL Server 2005 to follow the password policies defined at the OS level. This breaks our application in a subtle way in that we create login accounts for new client databases with random password. Because the password is random it sometimes conforms to the policy and sometimes not.
In production environments, the password policies are configured differently. So I need to one of the following options:
-change the group policy/inherited policy on my machine to not inherity from the domain I joined (prefered solution but don't know HOW)
-change SQL Server to not use OS password policy
-change code to use CREATE LOGIN statement with CHECK_POLICY=OFF or change password generation code to use a stronger password. (don't want to do this as the code change is only accomodating non-production environments)
If someone has a better place to post this question, I would sure appreciate it.
I put this together to export the user name /password to a csv file to test my SP to output the user name/password.
DECLARE @user_name varchar(50)
DECLARE @psswrd varchar(10)
SELECT @user_name ,@psswrd
FROM ngweb_bulk_enrollments
EXEC master.dbo.xp_cmdshell 'bcp NGDevl.dbo.ngweb_bulk_enrollments out C: est.csv -Sserver1 -T -t, -r
-c'
This works but I don't get the headers in the file. How can I include the headers?
Hi,I have developed site which has a resource file which connects to sqlserver using login name and password.Now my client doesn't want me to login to production database. bu the packing of the system is with me. is there any way to solve this issuse so that i can package the software without knowing database login name and password.TIAAmit
View 2 Replies View RelatedI read in Computer Weekly (Jan 6th 2000) about a bug in SQL Server 7. This means that any user can get hold of the administrator (sa) password.
Does anyone know anything more about this ??
thanks
Paul
Hi,
I reset user passwords on SQL Server 6.5 when users forget them. How can I do this without
using Enterprise Manager? Is there a stored procedure that I can call from iSQL?
Thanks,
girija