Viewing 15 posts - 21,451 through 21,465 (of 22,189 total)
You've got a slight syntax error. Your code should look like this:
CREATE TABLE BATCHES_LOT_DETAILS
(
[BATCHNO] varchar(15)
,[CALCULATED] char(1)
...
November 29, 2007 at 7:02 am
That last error sounds like you either aliased the table and then referred to it by name or that you dropped the table prior to that part of the script...
November 29, 2007 at 6:50 am
Or do a search in the little box near the top of the page. You'll find tons of discussions and articles and scripts on the topic, all on this site.
November 29, 2007 at 6:45 am
As far as I know, you're going to have to monitor that table. That means setting up some type of service to check the table periodically and respond to the...
November 29, 2007 at 6:27 am
Do you mean something like this:
ALTER TABLE dbo.X
ADD CONSTRAINT MyConstraint
FOREIGN KEY (aa,bb)
REFERENCES dbo.Y(aa,bb)
Like that?
November 29, 2007 at 6:16 am
BOL should give you most of what you need.
I strongly recommend using the TSQL commands to run the profiler job, not the gui. I also recommend placing the output...
November 28, 2007 at 12:30 pm
I didn't see it, so I'd add the TextData column as well. Other than that, you've covered the basics.
November 28, 2007 at 12:21 pm
You don't need the Profiler gui. Actually, better still if you don't have it. There are several ways you can get the scripts, including generating them locally through your own...
November 28, 2007 at 8:45 am
Gather statistics on both sides of the equation. Guessing or pointing at various bad signs won't help. You need a reasonably thorough picture of what is occurring. For example, do...
November 28, 2007 at 8:23 am
Two options, write a function that takes the comma delimited list and turns into a table or pass the list in as XML and use OPENQUERY or XQuery to join...
November 28, 2007 at 4:40 am
It's most likely the server, but I'd gather some information to back yourself up. Use profiler to get a days worth of data, hopefully including a timeout or two. Go...
November 28, 2007 at 4:37 am
Have you run Profiler to identify the poor performing processes? If not, I'd do that right away. You say it's a third party vendor. Once you've identified badly behaved procedures,...
November 28, 2007 at 4:33 am
Gail gave it to you
SET NOEXEC ON
Put that in front of the query with a semi-colon seperating it from your code. This works against Adventureworks:
SET NOEXEC ON;
SELECT * FROM...
November 27, 2007 at 5:14 am
Just a quick clarification, 2008 isn't supposed to ship until Q2 2008. Personally, I wish they'd wait until Q4, 2009.
November 27, 2007 at 4:58 am
If you want to parse it from your client, use the code that Gail provided from there.
November 27, 2007 at 4:55 am
Viewing 15 posts - 21,451 through 21,465 (of 22,189 total)