In SQL Server 2000, can you enable an option to check password retries? For example if an SQL Server ID logs incorrectly 5 times, you disable the login account.
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.
Hi everyone In my SqlServer Management Studio Express, on start up it shows the server type option, but greyed.So that value is fixed to database engine. ( I'm trying to work on an SqlServer Compact Edition database through the SSMStudiothat's why I'm trying to get this to change.)Besides, after I connect i go to the Object Explorer, expand the server node, and go to Replication.When i expand replication, i get the "Local Subscription" option, but nothng for Publication.( I want to work on Merge Replication, that's why I desparately need Publication to work)Am i missing something here? I did not install SqlServer separately, I only have what comes bundled with the Visual Studio 2005 Setup.
Are there any built-ins, utilities, ... within sql server 2000 that can be used to enforce password complexity in the database. i.e at least 8 characteres, upper and lowercase mix, includes at least on number and one punctuation (underscore,...).
I understand that this requirement can be achieved using windows authentication. Unfortunately we do not have that luxury (at the moment).
I 'completed' a DTS package which uses a file on a non-SQL server. I am about to put this into production, so it runs automatically each evening. but just realized that it won't work unless it signs onto the source file's Windows 2000 server. It works for me when I'm testing it because I am always logged on the the Windows 2000 server.
I have been trying to figure out which DTS task I need to use to establish a connection by embedding my UserName and Password. Any tips woud be apprecitaed.
HI!I have a little problem:I have change the administrator password (Windows 2003 Server) which MSSQL 2000 use to login.And now the SQL server can't stand up.What should I do?thx!gicio--Posted via http://dbforums.com
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'm aware that when bulk loading to a SQL 2005 database through an OLE DB Destination, you can enable the FIRE TRIGGERS option. Is this option available when your database target is SQL 2000? I can't find it in the Properties or other windows.
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 realize this must be an unexpected question in this day and age of MS SQL 2005, however, at my company i need to upgrade from SQL 7.0 to SQL 2000 standard on a WIN2K machine.
can anyone out there tell me why the option to upgrade ("Upgrade, remove, or add components to an existing installation of SQL Server") is disabled ?
I'm reading that i should be able to upgrade without having to install a second instance.
This is more of a philosophical post, but feedbacks are welcome!
I am working at migrating SQL 2000 DTS packages that pulls data from MAS90 via ODBC connections. At first, I REALLY tried to learn SSIS and I hated it at first, with all the new things one has to do to get a simple import to work. After a while, I begin to appreciate some of the new design and the more tiered approach. Indeed, I tried to use SSIS to import the tables and even learned how to overcome the Unicode/non-Unicode conversion errors by using the Import Wizard to do the grunt work.
But today I came across a show stopper: My imports are failing because the source lied about its metadata type and I am getting a "Value too large for output column" error. I tried to recreate the Task to no avail. I searched on the web and there are very few posts regarding to this and unfortunately I don't have a way to tweak my ODBC connection properties for MAS90 to some how "fool" SSIS. I finally give up and migrate the DTS 2000 package instead.
I am not too happy about this solution because I know that more likely or not Microsoft will discontinue support for such legacy approach and then it is more work down the road. I REALLY wanted to do it right, to rebuild it natively in SSIS but why does SSIS have to make things so hard by enforcing the type checks so tightly? Is it so bad to allow users who know the data better to by pass the validations? We are not working in a perfect Comp Sci 101 world where every thing is scrubbed clean, we work in a world of bad, old, malformed data.
If there is a way for me to overcome that "value too large" error, I am all ears. Thank you for reading.
I am trying to change password, using the code below.. The code below is in a stored proc and I am passing these parameters from a web application..... sp_password [ [ @old = ] 'old_password' , ] { [ @new =] 'new_password' } [ , [ @loginame = ] 'login' ]
sp_password 'cust1','cust2','cust1' Server: Msg 15210, Level 16, State 1, Procedure sp_password, Line 20Only members of the sysadmin role can use the loginame option. The password was not changed. I made my user part of the db_securityadmin role, but that does not help... How can I give the above mentioned permissions, so that when user cust1 logs on then he can chnage his own password from the web application as long he has given his old password correctly?
Dear All! I have installed my sa password "sa" during my MSDE (desktop engine of sql) installation. currently i am loging into query analyzer using windows authentication. But i cant access the database through my code, coz i dont have sa access. Please kindly Help me finding my current sa password. Thank You!
Is it possible to set up some kind of error handler in VB using the DTS DOM that will enable a retry of a step/task within a package? This is a DataPump task with a Custom Task. I am transferring 16 tables within each of the packages, 1 package for each of the 50 states, and executing them 1 at a time from a VB app. I can retry a package from the package error handler but can't find an equivalent for a step or task. I'd rather not have to resend tables, but restart from the table with the problem.
It is possible to write code to recreate an abbreviated form of the package but I'd like to avoid that, too.
Better yet, how can I avoid this error even appearing:
"Execution canceled (sic) by user".
I'm not cancelling anything, but about every 4th package this error comes up, not even while transferring the same table. If I retry the package, it almost always flies.
I am looking to create an ASP w/ functionality to change user's SQL password. Many do not have access to EM or Query Analyzer and need a website to visit. Has any had expirience w/ this prior?
I have SQL 2000 and I forgot my SA password and cannot login as administrator using windows authentication.
Is there any way to reset SA password?
"Mixed Mode" authentication is enabled.
If I change authentication mode in register to Windows only and then after restarting SQL change it back to Mixed, will it reset SA password to "null"?
>When a conversation is marked delayed, Service Broker performs the matching process again after a timeout period. Notice that failure to find a matching route is not considered an error.
for example it could happen when there is no route for a service. the question is - what is this timeout. Is it configurable? on a system wide basis ?
It will be great if this process is described in more details.
I need advice on how to retry a Data Flow if it errors. There is one problematic data flow within a .dtsx w many other data flows. The DF is a relatively OLE DB Source to OLE DB target task, except that it is long-running and sometimes gets timed out at the source. Not sure how to do it with the event handler. Any advice appreciated.
Hello, I'm running an MS SQL 2005 database which supports our entire website and it's fairly huge. I seem to have lost the sa password for the database.
I COULD get it back if there was a way to convert the SQL 2005 DB to an SQL 2000 DB, seeing as how I found a password cracker for that version. Is there anyway to convert a 2005 DB back to a 2000 DB?
Does anyone have any other ideas they might want to lay on me?
I'm kind of sick about this... I'm usually a really good note-taker; In fact, I do have the sa password recorded in an IT database that I keep. Unfortunately the password just doesn't work. I've tried the caps lock and other variations, but the password just eludes me.
Hello, I'm running an MS SQL 2005 database which supports our entire website and it's fairly huge. I seem to have lost the sa password for the database.
I COULD get it back if there was a way to convert the SQL 2005 DB to an SQL 2000 DB, seeing as how I found a password cracker for that version. Is there anyway to convert a 2005 DB back to a 2000 DB?
Does anyone have any other ideas they might want to lay on me?
I'm kind of sick about this... I'm usually a really good note-taker; In fact, I do have the sa password recorded in an IT database that I keep. Unfortunately the password just doesn't work. I've tried the caps lock and other variations, but the password just eludes me.
I am implementing the first Sql Service Broker use case in our Sql 2005 application, so forgive me if this is an obvious question. We will be using a service & queue to handle requests to download a batch of documents from a third party service. The basic workflow is: A. Web client requests a document download. B. Web application begins a conversation and sends a message requesting the download C. DownloadService stored procedure retrieves the message and attempts the document download. D. If the download fails, retry every 30 minutes up to max 5 attempts.
Other than (D), this is perfectly straightforward. I will describe the design I've come up with to retry after 30 minutes below. I would appreciate any suggestions on better ways to handle this within SSB.
My solution relies on a small state table: create table MessageState ( ConversationHandle uniqueidentifier NOT NULL, RetryCount int NOT NULL, MessageBody varbinary(max) NOT NULL )The web client begins a conversation and submits a message. It does not end the conversation, but rather the InitiatorQueue has an activation procedure to end its side of the conversation after the DownloadService ends them, as described here http://blogs.msdn.com/remusrusanu/archive/2006/04/06/570578.aspx.
The DownloadService logic, in pseudo-code: 1. Use a typical loop to get conversation groups and receive messages 2. If message type = DownloadRequest 2a. Call a stored procedure to attempt the download 2b. If successful, end conversation 2c. If not successful, add entry to MessageState and BEGIN CONVERSATION TIMER with a 30 minute timeout 3. If message type = 'http://schemas.Microsoft.com/SQL/ServiceBroker/DialogTimer' 3a. Look up conversation handle in MessageState 3b. Recall original MessageBody 3c. Call a stored procedure to attempt the download 3d. If successful, delete MessageState row end conversation 3e. If not successful and no retries left, delete MessageState row and end conversation with error 3f. If not successful and retries remaining, increment MessaageState.RetryCount and BEGIN CONVERSATION TIMER with a 30 minute timeout
The main downside I see to this solution is a certain lack of transparency. After step (2c) or (3f), "select * from DownloadQueue" will no longer show the pending request, although you can find it in sys.conversation_endpoints.
Is there a better idiom to solve this type of problem in SSB?
If I want to download a file, but I don't know if it's available yet (actually positive it won't be available for some time), how do I make FTP Task retry/wait until file shows up in the ftp folder?
I have a flat source file(.csv) which I am importing to SQL server. Now, if the source file is not available at the specified location, then the SSIS package should retry to execute n times( say 3 times) after certain time interval. The number of retries and the time interval should be configurable.
I have used Flat File connection manager for the source and OLEDB connection manager for the destination.
I am quite new to SSIS. Any help would be highly appreciated.