Viewing 15 posts - 47,056 through 47,070 (of 59,101 total)
First step of becoming a DBA is learning how to find stuff like this out... visit the Microsoft WebSite.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 11:30 pm
Not my idea, but... find's files for current database and makes a report of used, unused, and total size...
select [FileSizeMB] = convert(numeric(10,2),round(a.size/128.,2)),
[UsedSpaceMB] = convert(numeric(10,2),round(fileproperty( a.name,'SpaceUsed')/128.,2)) ,
[UnusedSpaceMB]...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 6:24 pm
thusi (11/23/2008)
Just letting you know that I did manage to write some sequential code to do this. Don't think you can simply do it in a single sql statement..so...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 6:19 pm
technicx101 (11/16/2008)
I have a table with 33 columns of Skill types e.g. Skill1, Skill2, ..etc. A particular skill, say, "C#" can be found in any of the columns. Basically...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 6:17 pm
I'm pretty sure that there is... attach one of the files and a record layout and let's see what we can do...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 6:14 pm
It's simple... one of the two columns you join on is an INT... the other is not and contains a number larger than what an INT can handle.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 6:06 pm
So, how did things turn out?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 5:49 pm
Ria (11/21/2008)
Thanks Phil..It works now
Umm... what about the things that start with "A"?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 5:41 pm
The answer is, what day of the week did date "0" occur on? Then, look at the (-1) and all will become clear.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 5:30 pm
Mad-Dog (11/23/2008)
thanks for your replays.i can't touch the query because it come directly from the ERP(Priority).
can i do something else (beside DTA)to check this query to get better performance?
THX
Ok... no...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 5:14 pm
Grant Fritchey (11/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 8:35 am
Man, I'm with Jack... use 2 or 3 part naming in the FROM clause, add aliases, and then use the aliases everywhere else. Done properly, it makes the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 8:19 am
Grant Fritchey (11/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 8:11 am
Grant Fritchey (11/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 7:11 am
I agree with Gail... you need to tell us "Why" you want/need to do this to make sure we give you the best solution.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 23, 2008 at 6:59 am
Viewing 15 posts - 47,056 through 47,070 (of 59,101 total)