Viewing 15 posts - 136 through 150 (of 236 total)
Hi,
I also get the Object Required error at line 64
Error: -2147220482 (800403FE); Provider Error: 0 (0)
Error string: Error Code: 0
Error Source= Microsoft VBScript...
If it ain't broke, don't fix it...
February 26, 2006 at 6:21 am
Hi,
have you tried running this query through the Query Analyser with the Show Execution Plan or display Estimated Execution plan option. It may be that your statistics for one of these...
If it ain't broke, don't fix it...
February 22, 2006 at 2:32 am
I think Toad for SQL Server (60 days freeware trial version from Quest software) includes this feature.
David
If it ain't broke, don't fix it...
February 15, 2006 at 4:32 am
Hi,
Have a look at the sp_processmail procedure in the master database. This examines an inbox and executes the SQL query sent in the email, returning the results as an attachment....
If it ain't broke, don't fix it...
February 15, 2006 at 4:10 am
Hi,
you can write a UDF that returns a table variable containing all the dates between start and end date inclusive...
CREATE FUNCTION udf_DateRange (@dtStartDate DATETIME,
@dtEndDate DATETIME)
RETURNS @DateRange TABLE
(InDate DATETIME)
AS
BEGIN
...
If it ain't broke, don't fix it...
February 9, 2006 at 2:39 am
This may sound like a silly question, does the schema you are trying to use exist in the database you are connecting to? What happens if you name the database explicitly?
David
If it ain't broke, don't fix it...
February 9, 2006 at 2:16 am
My first job was supporting Oracle 5 on a Pr1me mainframe. We had 20Mb of disk space, and the system could support about 70 concurrent users.
I only had two...
If it ain't broke, don't fix it...
February 9, 2006 at 1:56 am
Hi,
does anyone have any thoughts on this, or have they been able to reproduce this effect?
David
If it ain't broke, don't fix it...
February 8, 2006 at 7:47 am
Hi,
Backing up the database and transaction logs to tape is fine if you only ever need to restore the database as a whole, or to a particular point in time.
Many...
If it ain't broke, don't fix it...
February 7, 2006 at 4:54 am
I encountered a problem of this nature, when I found that the system i administer had a varchar field containing dates. When you sort the dates they come out in...
If it ain't broke, don't fix it...
February 1, 2006 at 6:33 am
Hi Chris,
I'm not an expert, but my comprehension is that when comparing strings, SQL Server does a character by character comparison of the ASCII codes, starting with the leftmost characters....
If it ain't broke, don't fix it...
February 1, 2006 at 2:18 am
In the menus, Tools, Options and go to the Connection Properties tab, you can set NOCOUNT and ANSI_WARNINGS there. But make a note of your currentsettings, it is also worth...
If it ain't broke, don't fix it...
January 25, 2006 at 2:43 am
The examples in BOL of using the FROM clause in an update seem to be inconsistent. It doesn't seem to me to be clear whether you have to specify the...
If it ain't broke, don't fix it...
January 25, 2006 at 2:34 am
You could also try recompiling all the stored procedures using
EXEC sp_msForEachTable 'EXEC sp_recompile ''?'''
And refreshing the views using sp_refreshview.
I had problems on my system, poor performance and data missing from...
If it ain't broke, don't fix it...
January 25, 2006 at 2:03 am
So at the risk of asking a junior DBA question, don't leave us in the dark, how would you change the thread priority? ![]()
I...
If it ain't broke, don't fix it...
January 24, 2006 at 3:00 am
Viewing 15 posts - 136 through 150 (of 236 total)