Hi, for some AP issue, the file I upload must be without the line feed/carriage return in the last line. for example:
original fixed-length file (exported from SSIS) line NO DATA 1 AA123456 50 60 2 BB123456 30 40 3 CC123456 80 90 4 <-- with line feed/carriage return in the last line
The file format that AP request. The file only has 3 records, so it should end in the third line. line NO DATA 1 AA123456 50 60 2 BB123456 30 40 3 CC123456 80 90
Should I use script component to do it ? I am new for VB . Anyone would help me ?
I need the Trend line for the following data in Line chart they are the following data. The following are the graph are my output and i need the trend line for these Key_gap value.
This is the link [URL] ....
I need the same trend line for the Bar-Chart in SSRS 2005.
I hope I'm posting this in the correct forum (forgive me if I'm not) since I'm not sure if this is an issue with inserting an item into a db or the processing of what I get out of it. I wrote a basic commenting system in which someone my post a comment about something written on the site. I wanted to keep it very simple, but I at least want the ability for a user to have newlines in their comment without having to hardcode a <br /> or something like that. Is there a way for me to detect a newline if someone, for example, is going to their next paragraph? Let me know if you need a better explanation. Thanks in advance!
Is anyone using the -DelBkUps option with their maintenance plan on SQL 7.0?? if so is it actually deleting the files? Mine is running but not deleting any of the old backup files.
I would like to run the following SQLMAINT command on my database every 14days:
At 2:00 AM, this command needs to kick off: SQLMAINT.EXE -D cabinet -CkAl -CkCat -UpdSts -RebldIdx 100 -Rpt D:MSSQLLOGcab_maint.rpt
Question: How can I "kill" all users, then place the database in "dbo" mode, run "SQLMAINT", and then release database access back to the public - all in an automated process.
Was wanting to get some feedback on using sqlmaint to produce database backups in a production environment. Especially on databases > 10GB. My preference is not to use it but I'm arguing with another DBA and wanted some outside feedback.
G'day everyoneThat's a space between the ticks.It's all part of a longer script but seeing as the failure occurs online 1if exists (select * from dbo.sysobjects where id =object_id(N'[dbo].[config]') and OBJECTPROPERTY(id, N'IsUserTable') =1)drop table [dbo].[config]GOThat's three lines only. Does it matter that they're in Unicode?Any ideas?Kind regards,Bruce M. AxtensSoftware EngineerStrapper Technologies
I am a big fan of the backup naming convention used by maintenance plans and the SQLMAINT utility. My problem is that I want to use the same naming convention "db_name_diff_YYYYMMddhhmmss" because of my situation: I'm in California, my databases are in Pennsylvania, I don't have domain access to the servers, I use a scheduling tool (required) that only uses T-SQL or cmd line utilities, and I want the backups named as above. SQLMAINT provides for full and tlog backups, which I have set up, but I want to do diff backups the same way, with the same naming convention. Any ideas?
I run the SQLMAINT.EXE utility nightly to do DBCC checkdb, checkalloc, and checkcat checks on all databases. On one server this check seems to lock up the server displaying error 17832, "unable to read login packets". Once this occurs the only way we can find to get out is to reboot the NT Server. We have observed this behaviour once every two or three weeks. Anyone seen anything similar?
SQL2000 SP3a I would like to generate an HTML output file as a report which should be possible. After creating the maintenance plan using the wizard I used the created syntax and established a second job which now uses the changed syntax - however the job doesnt run. In the log file it just states the basic sqlmaint switches. Current job syntax - SQL uses build in system account.
I have a maintenance plan on a client's site, there's only one databasein the plan and it's set to backup db and log, this job failsconsistently. The one step in the job contains this line:EXECUTE master.dbo.xp_sqlmaint N'-PlanID392B2334-6800-4655-A6C7-5414D9072505 -WriteHistory -VrfyBackup-BkUpMedia DISK -BkUpDB "C:Program FilesMicrosoft SQLServerMSSQLBACKUPDailyBackups" -DelBkUps 4WEEKS -BkExt "BAK"'Which fails if run in QA with the message:Server: Msg 22029, Level 16, State 1, Line 0sqlmaint.exe failed.I've searched for this error and cannot find anything to help.There's no "-S" in the path, it writes absolutely no history on theplan. I set the plan to write history in the log directory on theserver, it wrote nothing to that directory.The database doesn't get backed up but is able to be backed up manuallyto the path specified in the plan. I also have a separate job with aSQL backup statement in it that works OK so SQLAgent is working.
I am using SQL 2000,everyday we are running database backup plan but it shows a error like "Executed as user: NT AUTHORITYSYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." Our database recovery model is also in Full mode.Burt i don't know why its happening with us,before that database maintenance plan was working fine but for last 2 months its not working.
We have a line graph which plots the actual data points (x,y), everything is working fine with this graph. Now we need to add a trend line to this existing graph after going thro. the articles we came to know that there is no direct option in SSRS to draw a trend line. So we need to calculate the trend values ourselves which we need to plot as atrend line. This trend line is similar to the trend line which comes in Excel chart, do anyone know how to calculate the trend values from the actual data points. We got through several formulas, but were not clear, have anyone tried out exactly the same, if so please help us out by providing an example to calculate the trend values.
I have a line graph which shows positive and negative values. Is it possible to have the line one color when its negative and another when its positive?
I have a situation where I am running sqlmaint on 10 - 12 databases on the same server. All of them run successfully; However, one returns a failure because of no message. MSDB is not full. There is no messages in the errorlog. And the actual SQLMAINT executed just fine.
I'm running SQLMaint.exe for DBCC and backups overnight, because I like the -BkUpOnlyIfClean switch, but I'm having a problem. I need Due to space constraints, I need to overwrite the backup every night. The -DelBkUps switch is nice, but it accepts a parameter of weeks, not days. Is there some syntax I can use with SQLMaint.exe to get what I want, or am I going to have to do an NT 'at' commnad to get rid of the file just before th enext dump, or what? Any suggestions would be intensely appreciated.
I installed a new SQL Server and implementd a maintenance plan for user databases. In doing so, all the jobs seem to work except the Integrity checks. These jobs fail with the following error: sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Has anyone seen this? Or has an idea how to fix it?
Hi! I have a SQL 7.0. The backups created by maintenance plan workedvery well before someone shut down the server to do some servermaintenance. After restart the server, the backup job is not workingany more. All the backups created by maintenance plan are not working,including the newely created one. The message is "Server: Msg 22029, Level 16, State 1, Line 0sqlmaint.exe failed."Please help me out!! Thanks.Saiyou
Both "dump database" and "sqlmaint.exe -bkupdb" would be able to backup database, one important advantage I can see from "sqlmaint" is that it has the option to cleanup the very old generations of backups by using -delbkups option in a scheduled maintenance backup job, while the "dump database" would first create a dump device and it'll grow with time. Is there any suggested way to use the "dump transaction" but still we can get control on the size of dasd used ? Any negative part of using "sqlmaint" utitity to backup database as compared to the "dump database " utility ? Anthony
We run SQLMaint hourly ( as a scheduled task ) to clear our transaction logs. Last night our hard drive filled up during a log dump, causing SQLMaint to fail, and a subsequent transaction filled up the log.
We succeeded in manually truncating and clearing the log, but SQLMaint still insists on us doing a DUMP DATABASE to clear the logs before it will run again. Unfortunately, we do not have enough space left on our hard drive to do a full database dump.
Is there any way of fooling SQLMaint into believing that a DUMP has been run? Some flag in a system table somewhere, or maybe a registry entry?
My SQLMaint integrity checks consistently fail when the "Repair any minor problems" option is checked. The reported reason is that the database must be in single user mode. This doesn't seem practical. Am I missing an option somewhere?