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?
Hello - I am aware of the new password policies in SQL Server 2005, but I have not seen this yet. Can anyone please tell if it is part of the new software?
When a password has been reset, you can force the user to change it upon initial login?
I have query that calculate a running balance, but I need to reset that balance when it reaches 240. Then start calculating the balance again from that value. For instance, let's see we have the following table:
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?
I am having a problem with Cascading Parameters in a RS2005 SP2 report. In the report the user selects the part # (param 1) based on the part number selected the serial # list (param 2) is populated. This all works fine.
The problem is that when the user clicks on the View report button the report is generated and the part # stays the same but the serial # parameter is "reset". On the development box it gets reset to the last serial # on the list. When we deploy out to our production environment it gets reset to the first serial # in the list.
Is there a way to stop the serial # (param 2) from being reset and to have it stay to what the user selected.
Whenever I apply a hotfix to my SQL 2005 install, the folder permissions on :Microsoft SQL ServerMSSQL.1MSSQL are always reset. Any reason why this happens? I have explicit permission set on that directory to allow our DBAs access as they are not admins on the server.
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.
I discovered that everytime I need to add a database to my backup Maintenance Plan, after I select the new database from the drop-down of databases, the Destination automatically resets back to a default location.
I'm assuming this is a bug that will be resolved at some point, but in the meantime, I need to see if there is a way I can deal with this permanently. I am not the only one adding databases to the backup routine so I can't verify that this setting is properly changed every time we have a new database (which is about once a week).
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.
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.
I 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.
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?
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.
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
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
This is the first time I am using SQL Server 7.0 on a bussiness machine, I need to apply password on the database, OS is windows XP professional, need u r help on this.
I have developed a stored procedure that create linked server. The problem is: to crearte the linked server I need to pass user and password. How can I pass user and password in a encrypted way. I think that if the stored proc execute: addlinkedserver procedures with user and password, these are readable to everybody with sniffer or SQL profile.
How can I pass encrypted password to SQL server engine to create a linked server?
I am trying to find out how to hide/obscure a password in SQL server. Currently the passwords are being held as a text field, which means that anyone who queries the table or just opens it can see everyones passwords.
Is there some way of hiding this? I have been searching for ages and can't seem to find anything.
I have developed a stored procedure that create linked server. The problem is: to crearte the linked server I need to pass user and password. How can I pass user and password in a encrypted way. I think that if the stored proc execute: addlinkedserver procedures with user and password, these are readable to everybody with sniffer or SQL profile.
How can I pass encrypted password to SQL server engine to create a linked server?
I am in a panic right about now. We had to change the Admin (server) password and it is working fine to log on to Windows, but when I click on IE and navigate to the report server, it is asking me for the old password still. I am new to SRS, so I am learning as I go. I found some threads on using the rsconfig.exe and I fiddled around in it and now (in addition to requesting the old password to log on to the report server) all of the reports I created have a user name and password field that requires the SA password for connecting to the data source.
Is there any way I can fix this or do I just need to uninstall SRS from the server and re-install it? I found the following thread, but am a little skiddish about doing anything else in light of the current state I put the report server in.
I have forgotten password of user sa in sql server 2005. But if authentication is window . I still login, and do work normal. So how to solve problem ,if authentication is sql server. Thank you very much.
Hi Guys,We've lost the password for the sa. No other users belong to the admingroup. I've tried logging in using osql -E (windows authentication)without success. Is there anyway to reset the sa password? The databaseis MSDE and the version seems to be 7 (sql server 7 folder on pc). Itis running on Windows 2000 professional.Any help would be greatlyappreciated.Regards,Eddie
Hi, I'm using the SQL Server Everywhere CTP on the desktop and haven't used SQL Server Mobile in the past.
I'm having some difficulty determining whether it's possible to change a SQL Server Everywhere database's password. Obviously authentication on a file-based SQL Server Everywhere database differs from that of server-based SQL Server database. Is it possible to change a SQL Server Everywhere database's password?
That said, I feel like I've made a decent search of the to change a SQL Server Everywhere books online. If it's not possible to change the password in place (i.e., without copying all data to a new file with a different password), please count this as a vote to add that functionality. Making a database password "permanent" lessens its effectiveness. Thanks,