Viewing 15 posts - 31 through 45 (of 358 total)
I can think of two places you should look. The first query is for the database file locations and the second query is where the dll's are located.
SELECT SUBSTRING(filename,1,1)...
June 11, 2009 at 11:12 am
I think you are looking for something like this...
select text from sys.messages where message_id = 101 and language_id = 1033
June 10, 2009 at 11:35 am
Open the Maintenance Plan In Management Studio and at the very top there is a little icon that looks like two reports (right next to Manage Connections). Click the icon...
June 10, 2009 at 11:27 am
Try this.
SELECT CONVERT(VARCHAR(10),CAST(date_id AS DATETIME),101)
FROM Summary_D
Also, what data type is date_id?
June 10, 2009 at 11:22 am
Try this...
Select
SUBSTRING(physical_name,LEN(physical_name)- CHARINDEX('\',REVERSE(physical_name))+2 ,LEN(physical_name))
FROM sys.master_files
June 9, 2009 at 1:46 pm
I think the default trace that is running in SQL Server will capture this information.
--Run this query to get the current file name and place it in the path for...
June 9, 2009 at 9:36 am
Here are some scripts I use to show the jobs and thier related schedules. You should be able to use this to see how the tables are related.
June 4, 2009 at 3:01 pm
This might help get you started. Notice that longer views are broken into multiple lines.
select B.name, A.text
FROM syscomments A
JOIN sysobjects B
ON A.id = B.id ...
June 1, 2009 at 9:32 am
I was about to ask the same thing as Gail. Here are some things you should do when upgrading...
--Update Statististics with Fullscan
Exec sp_MSForEachTable 'Update Statistics ? with FULLSCAN'
--The following...
May 29, 2009 at 2:16 pm
Resample is a good idea to make sure you don't overwrite the full sample by the index rebuild. You still may end up doing duplicate work, depending on how busy...
May 28, 2009 at 12:11 pm
If you don't need to update your statistics with full scan - then you should use the procedure sp_updatestats which will only select statistics that need to be updated.
...
May 27, 2009 at 10:27 pm
I think you are talking about something like this. I just used 5 records in the example. Also, what version of SQL are you running?
--Begin Test Data
DECLARE @tbl Table(id varchar(10),...
May 26, 2009 at 10:02 am
That is because SQL is converting the string to a datetime so the datatypes are compatible in the case statement. If you convert the date to a varchar, the...
May 22, 2009 at 9:16 am
Yelena Varshal (5/22/2009)
There are 2 workarounds in BOL:
http://msdn.microsoft.com/en-us/library/ms179859.aspx
Read in this page under these subtitles:
Using Wildcard Characters As Literals
Pattern Matching with the ESCAPE Clause
Let us...
May 22, 2009 at 9:06 am
I cut and pasted the first box and got this to work.
Declare @Table Table (tst nvarchar(100))
Insert into @Table Values ('"3C3Z*8620*BC[m[H[" ')
Select * from @Table
Where tst like '%%'
May 22, 2009 at 8:52 am
Viewing 15 posts - 31 through 45 (of 358 total)