aw comeon Mh;

with 170+posts, I KNOW you know better.

Always post a table structure and insert statements so people can help you.

here's a fake table and data for others to try...

Casper (3/30/2009)

---

yeah i thought auditing would have to be the way out.

Just by the way - you said "if not too much time has passed" i can use the default...

if not too much time has passed, the default trace can help:

-- obtain file name for Default Trace

declare @TraceFileName nvarchar(256)

set @TraceFileName = (select path from sys.traces where is_default =...

Krishna was alluding to the "sa" username and password on the SQL server for sysadmin rights. since it looks like someone removed access for BUILTIN\Administrators, where all the local and...

yes...you can take a SQL 7 or 2000 backup and restore it on a SQL2005 server; the restore automatically upgrades it to the newer format; you just cannot do the...

here's an article i saved on parameter sniffing; basically, the default for an execution plan is to look at the statistics to determine how unique the parameter is; but when...

that's the expected behavior:

if you compare anything to null, the results are undefined...

so you either want to add a where clause like ...AND A.DATE IS NOT NULL AND B.DATE IS...

parameter sniffing maybe? have you isolated which proc slowing things down? does it have a default value for any of it's parameters? in my experience, it's the default values that...

i tried running the command over a linked server; basically i tried changing the last command to a 4 part command:

EXEC linkedservername.master..xp_regread 'HKEY_LOCAL_MACHINE', @inst, @inst1

got this error:

SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS\MSSQLServer\SuperSocketNetLib\Tcp\\\\////TcpPort

Msg 7411,...

the BETWEEN oerator is what you want i think;

select * from sometable where invoice_date BETWEEN '01/01/2009' AND GETDATE()

you said how to select max date's each home , location and status.

like lynn said, all the tools are there...run this, test it, and drop the columns you don't need.

indexes become fragmented due to inserts.

say you have an index on "LastName".

if i insert someone whose lastname starts with "S", it will probably fragment the index, as it forces anew...

a GO statement ends your procedure, and runs the next command; you've pasted commands INCLUDING the "GO" which is not what you want.

this is a better format:

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER...

just a simple grouping is what i would use;

note how i put your data into CREATE and INSERT INTO so that others could use it as sample data? that's a...

it sounds like a network issue...maybe DNS/WINS?

at the end, it says the IP is 165.193.92.4. is that an IP Address on your network?

does your connection string use the name of...