Viewing 15 posts - 1,366 through 1,380 (of 1,583 total)
This shouldn't be difficult, comment the code by it's workable sections 😉 Clearly code that's "SELECT this, that, and the other thing from some TABLE" shouldn't be heavily documented...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 16, 2011 at 9:56 am
Yeah, I don't recommend it either George 🙂 Just saying it should work and I would never disable the backup job anyway, I'd leave that running on it's regularly...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 15, 2011 at 8:50 am
Don't know too much about the functionalities in R2, but Agree with the prior post on "why", however if you want to add that check into the mix...
Write a...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 14, 2011 at 2:47 pm
By any chance when you added in the 3rd package, was it a copy from one of the others? Or was it a brand new package?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 14, 2011 at 2:12 pm
Do you have remote connections and xp_cmdshell enabled?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 10, 2011 at 1:54 pm
Yeah that's what we arrived at as well...was just hoping for magic... 🙂
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 9, 2011 at 1:17 pm
If they're using an ODBC connection to connect to the DB then and they will be completely limited to the SQL account being used in the ODBC connection. In...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 7, 2011 at 2:35 pm
Gail, the update locks are set by the developers of the application. I've ask them the same question and their reponse was along the lines that the application was...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 7, 2011 at 1:04 pm
I assume you are reffering to a web form of sorts? Need to know additional information about the end result...how have you set up the database table set up?...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 7, 2011 at 12:34 pm
You could accomplish this two ways:
Option #1
- Create a script to drop all your FK constraints
- Create a script to create all your FK constraints
To do this, right click on...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 6, 2011 at 11:41 pm
The Service Broker basically relays the mail from SQL directly to Exchange or your SMTP server (depending on how your architecture is set up).
If that's hung, the only...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 6, 2011 at 11:29 pm
Focus on this:
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".
Can you include...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 6, 2011 at 11:16 pm
I hate to ask this and even remotely offer it as a solution but...
Have you tried restarting the MSSQL service or rebooting the box?
EDIT :: Sorry Jared, I didn't see...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 6, 2011 at 8:28 am
Yes, as John states, "sqlcmd is preferred to osql"
Try that instead (and apologies for giving you the bad code!)
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 5, 2011 at 9:14 am
Have you tried using a TRY..CATCH block wrapped around the INSERT statement, this will allow you to do something after trapping/planning for the potential error, Ex:
BEGIN TRY
...
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
October 5, 2011 at 8:42 am
Viewing 15 posts - 1,366 through 1,380 (of 1,583 total)