Viewing 15 posts - 31 through 45 (of 66 total)
Check the size of the transaction log (using Enterprise Manager, right click on the database/Properties/Transaction Log. Check the size of the data file as well.
If the log is of a...
March 29, 2007 at 1:51 pm
Make sure you have a "guest" user in both databases. If it's missing, just add him (or her as the case may be 🙂
March 29, 2007 at 1:38 pm
I believe that you'll be in violation of license if you use a single processor license on that machine. I don't think that you can restrict SQL Server to use...
March 29, 2007 at 1:34 pm
I think the guy wanted you to answer in writing so that he could take the answer to the guy who wrote the question to see if it was correct. ...
March 28, 2007 at 3:48 pm
Here's the cursor code in case you need it (you shouldn't) Change the table names in the code from newtable and oldtable to the real names.
declare @signonid int
declare c cursor...
March 28, 2007 at 2:23 pm
I just thought of an easier way.
insert into newtable
(BranchID,emplID, Signin_Date, Member_Name, Member_No, Gender, empl_Pickup_Time, empl_Complete_Time, Reason1, Reason2, Reason3,Remarks, "Appointment?", Appointment_emplID)
select
BranchID,emplID, Signin_Date, Member_Name, Member_No, Gender, empl_Pickup_Time, empl_Complete_Time, Reason1, Reason2, Reason3,Remarks,...
March 28, 2007 at 2:07 pm
Ok, before I create the code, please try the following on the table.
update query set signon = signon + 125000 (or change 125000 to any number you prefer)
Let me know...
March 28, 2007 at 2:02 pm
Sorry, I steered you wrong on the update of the identity column, it can't be done. If you send me the list of columns for your table, I'll send you...
March 28, 2007 at 1:21 pm
I just read your post more carefully. With column name "signon" then the proper syntax is:
set identity_insert dbo.query on
update dbo
March 28, 2007 at 1:13 pm
there's a space on your SQL for the column "identity signon" The query should be:
set identity_insert dbo.query on
update dbo
March 28, 2007 at 1:08 pm
are you sure that the user who runs the SQL Server and SQL Agent services has the same rights as the user who runs the .cmd file from the command line? ...
March 28, 2007 at 11:42 am
There are some options, none of them pretty.
1. create a hole for your data. That would involve updating all the identity numbers for the current data to something higher than...
March 28, 2007 at 11:17 am
Yes, I've had that problem as well. My fix, though probably not optimal is to execute the query in isql and redirect the output to a file. In order to...
March 28, 2007 at 11:10 am
Is your application passing the parameters in a way that might fool SQL server into thinking that a decimal is an integer (for example). To clarify, suppose that one of...
March 28, 2007 at 11:04 am
try putting double quotes (") around the troublesome column name.
March 28, 2007 at 10:52 am
Viewing 15 posts - 31 through 45 (of 66 total)