Showing posts with label command. Show all posts
Showing posts with label command. Show all posts

Monday, March 26, 2012

Help! SQLEXPRESS Command Prompt Installation!

i have a problem installing SQLEXPRESS via command prompt... the installation is successful but the 'sa' account could not login to the server.. here's the command in my batch file.

Code Snippet

Start /wait <exe> /qb INSTANCENAME=MYINSTANCE ADDLOCAL=ALL *AUTOSTART=1 RSCONFIGURATION=DEFAULT SECURITYMODE=SQL SAPWD=sapwd SQLCOLLATION=Latin1_General_BIN requiresmsiengine=1

and one more thing, i need to run the report server automatically.. thanks! Smile

Which connection string are you using to connect to the database and which exact error message do you get ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||im using mixed mode... actually there is no error during the installation via command prompt it's just the 'sa' account could not login and the report server could not be initialized but all the components were installed... is there something wrong with my command in the batch file?

Monday, March 12, 2012

HELP! database restore using SQL Express

I've try to do the database restore in Microsoft SQL Server 2005 Express using sql command as below:

RESTORE DATABASE testJG

FROM DISK = 'c:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\Backup\JGsql.bak'

GO

But I get this error message.

Msg 3102, Level 16, State 1, Line 1

RESTORE cannot process database 'testJG' because it is in use by this session. It is recommended that the master database be used when performing this operation.

Msg 3013, Level 16, State 1, Line 1

RESTORE DATABASE is terminating abnormally.

Does this means that I need to restore the master database from systems database to the database testJG before I restore the backup database?

Give this a try....

With your query window active, make sure that the current database you have selected from the drop-down is the Master db and not the testJG database. That should free up your the active connection that SQL is complaining about.

You should then be able to execute your restore command.

Regards,

John

|||

Or, to be more explicit, add the command

USE MASTER;

to the beginning of your session, before the restore command.

|||

Owesome....it works...

thank you.....thank you!!! I love you guys....

that really solved my problem and I could successfully restore the database now....

Wednesday, March 7, 2012

HELP! " the table schema changed after the cursor was declared"

I have a DTS package working from backend and command line. Then I did an enhancement. It works from backend but not from command line. The error says:

Step Error Description:Could not complete cursor operation because the table schema changed after the cursor was declared.

But I don't see "table schema" change?!! Any idea?

Thanks,

LiliOriginally posted by lili3000
I have a DTS package working from backend and command line. Then I did an enhancement. It works from backend but not from command line. The error says:

Step Error Description:Could not complete cursor operation because the table schema changed after the cursor was declared.

But I don't see "table schema" change?!! Any idea?

Thanks,

Lili

I ran in to the same problem. As it turned out I was running the application at 1:00 am to process credit card transaction (This application is a batched response from shipper) Anyway. I had inadvertly schedule maintence during this time. The problem was resolved by moving the Maintence time.

I hope this helps.

Terry

Sunday, February 19, 2012

Help with Update Query command Problem

Hi all,

I have this store procedure as follows:

Create Proc UpdateProblem
@.ProblemID int,
@.CompanyName varchar (50),
@.Firstname varchar (50),
@.Lastname Varchar (50),
@.Address varchar (50),
@.Postcode varchar (50),
@.City varchar (50),
@.Phone varchar (50),
@.Cutype varchar (50),
@.ProDescript varchar (50),
@.Sol varchar (50),
@.Email varchar (50)

as Update Problem
set CompanyName = @.CompanyName,
Firstname = @.Firstname,
Lastname = @.Lastname,
Address = @.Address,
PostCode = @.Postcode,
City = @.City,
Phone = @.Phone,
Cutype = @.Cutype,
ProDescript = @.ProDescript,
Sol = @.Sol,
Email = @.Email


where ProblemID = @.ProblemID

when I test the querry

exec UpdateProblem
10004, 'Toro AS','Mike','Tullas','Togo Street','G34 5TT','New York','06582531','Private','Machine is dead','Replace motherboard','goo@.ht.com'

what happen is that when I ran the querry instead of updating the specifc row of 1004 the querry will just update the whole rows in the table with the same data.

Please help. I have set the ProblemID as the Primary key.

When you do a SELECT * FROM Problem WHERE PRoblemID = 10004 , do you get 1 row or multiple rows?|||Only 1 row when I run : SELECT * FROM Problem WHERE PRoblemID = 10004|||

Find out the error. where ProblemID = @.ProblemID --> wrong

where @.ProblemID = ProblemID -- Right

cheers

|||I dont think so. They are both same. There's something else that happened. ...WHERE ProblemID = @.ProblemID should work just fine. Thats the way most queries are written.|||Hi Justnew, is the ProblemID column defined as int type? Can you post some sample data so that we can repro your issue?