Viewing 15 posts - 1,186 through 1,200 (of 1,335 total)
In SQL 2005, you can use the SMO objects to create your database, table, column and more others. The code for the same is available in microsoft virtual labs sessions...
June 7, 2007 at 5:27 am
Yes of course.
70-431 for MCTS
70-447 for MCITP(Remember that MCTS is mandatory for this.)
June 6, 2007 at 2:20 am
Those are used when you want to create fulltext indexes in a table. To know more read full text index in bol.
June 6, 2007 at 2:19 am
The link below lists the availabl path for upgrade please check
June 5, 2007 at 12:46 am
Your insert statement itself seems to be wrong. It should be
insert into #temp select col1,..coln from tablename.
June 5, 2007 at 12:40 am
You can't create a table with the same name. If you would like to take backup of tables daily or periodically then you can use the script written by me...
June 1, 2007 at 7:33 am
In SQL Server 2000, you need sysadmin privilege to run profiler. The same is not the case with SQL 2005.
June 1, 2007 at 7:31 am
When you use local account yu can't access resources in network. Better change the account running your sql server and agent to a domain/workgroup account and grant the necessary permissions...
June 1, 2007 at 6:42 am
Just check if the given code below does work for you.
select substring(convert(varchar(30),getdate(),109),13,len(convert(varchar(30),getdate(),109)))
May 31, 2007 at 11:42 pm
If you have additinal hardware try implementing log shipping. But to take log back the recovery model should be either bulk-logged or full. You can't take a log backup in...
May 31, 2007 at 11:38 pm
Possibly the network bandwidth is veryvery slow. You can check these with the performance monitor counters that are avialable with the windows operating system.
May 30, 2007 at 3:20 am
Just change those settings and try executing the job to see if it succeeds.
May 30, 2007 at 3:18 am
A trigger, linked servers should be fine for your effort did you try that.
May 29, 2007 at 4:39 am
Just stop your SQL server service. thats enough. SQL server service closes all connections and then stops so there is no need for you to manually close all existing connections....
May 29, 2007 at 4:36 am
Yes as told by michael you have to reinstall .Net framework 2.0. Also go ahead with a clean installation of client tools from the machine you try to connect.
May 24, 2007 at 10:49 pm
Viewing 15 posts - 1,186 through 1,200 (of 1,335 total)