Viewing 15 posts - 271 through 285 (of 323 total)
Change the Log File auto grow property thro' SQL Server Management Studio.
(Select Database -> Properties -> Files...)
November 27, 2007 at 1:41 am
change the logic while exporting data into excel.
November 27, 2007 at 1:35 am
use ">> C:\Save.txt" instead of "> C:\Save.txt"
November 26, 2007 at 11:19 pm
can u explain your exact requirement. 😎
I think you may be expected like the following:
SELECT[Post_ID]
,[Post_Title]
,[Post_Reply_ID]
,[Reply_Title]
FROM[Cfamla].[dbo].[Post_Detail] pd
INNER JOIN [Cfamla].[dbo].[Post_Reply] pr ON (pd.[Post_ID] = pr.[Post_ID])
November 26, 2007 at 11:14 pm
Did u check my post...
Actually change the .txt file path to C:\Save.txt.
November 26, 2007 at 10:59 pm
Best information you can see SQL BOL. (http://msdn2.microsoft.com/en-us/library/ms130214.aspx)
November 26, 2007 at 10:57 pm
Hi Anu,
change the output path to "C:\Save.txt" and try it.
FYI:
----
Create Trigger TestTrigger1
On dbo.tablefortrigger
For Insert
As
Begin
Set nocount on
Declare @msg nvarchar(255) /*Check sp_addmessage */
Declare @CmdString nvarchar (2000)
set @msg = 'Inserted \ tablefortrigger \'...
November 26, 2007 at 10:46 pm
see the Setting Server Configuration section on SQL BOL or see the link: http://msdn2.microsoft.com/en-us/library/ms189631.aspx
or use Surface area configuration in SQL 2005
November 26, 2007 at 10:20 pm
more information on Index, refer SQL BOL. (http://msdn2.microsoft.com/en-us/library/ms189051.aspx)
November 26, 2007 at 10:09 pm
Try the following way:
DECLARE @sql VARCHAR(8000)
DECLARE @p_number NUMERIC
SET @p_number = 134070
SET @sql = 'SELECT * FROM M_Driemnd(' + CONVERT (varchar (10), @p_number) + ')'
PRINT @sql
🙂
November 16, 2007 at 3:13 am
you can find the SQL Server status using SQL-DMO object, refer to SQL BOL.
November 16, 2007 at 3:07 am
where & when you get error ?
provide code ?
November 6, 2007 at 5:34 am
If you have installed SQL Server 2005 completely (i.e. means includes samples), you can go to the samples folder and check the existing samples, so that you get some idea...
November 5, 2007 at 5:15 am
In SQL 2005 have no problem, but have problem in SQL 2000 and below versions. so better to move SQL Server 2005.
🙂
November 5, 2007 at 4:39 am
Viewing 15 posts - 271 through 285 (of 323 total)