In response to this tip, several readers submitted their own worst practices ? and now we?d like to hear from you. Whether you left system performance out of your requirements analysis or you know someone who has no dedicated development and test environments, send us your worst practice and you will be eligible to win a TiVo Series 2 40-hour DVR.
Please submit your tips here:

http://searchsqlserver.techtarget.com/tips/0,289484,sid87,00.html

Thanks for your time.

Nicholas Bellistri
Assistant Editor
SearchSQLServer.com

I’m the editor of SearchSQLServer.com and I am hoping to get your opinons on a timely topic.

Prior to Microsoft announcing its November 7 release date for SQL Server 2005, we had run a poll asking site members: How have the delays with SQL Server 2005 affected your organization’s plans?

58% delays had no affect
28% projects were being held up
13% may start considering other platforms

You can view the poll here:

http://searchSQLServer.com/r/0,,43739,00.htm?

I’m wondering where you fell in — if the delays have had any affect on your organization or opinion of Microsoft in general — and what your plans are now that the date has been announced. Will you upgrade right away? Will you wait until all the kinks are worked out? Will you not upgrade at all and move to another DBMS instead?

Please let me know when you have a moment. Comments will be included in a featured article on SearchSQLServer.com.

Thank you for your time!

Best regards,
Robyn Lorusso
Editor
SearchSQLServer.com

http://searchsqlserver.techtarget.com/

Now if I have server as ‘linkedserver’. Again I added a linked server in ‘SRVMAIN’ as ‘linkedserver’.
When I write a query as
SELECT * FROM linkedserver.TESTDB_new.DBO.TESTTABLE_new
I get an error message:
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near ”.
As linkedserver is an existing database, I cannot drop and rename it. It has huge amount of real data.
Pls help.

Is there any way to convert date format from UTC to PST?

Thanks and Regards

Ashu

I have been tasked with a difficult project.

My employer has a rather large database, hosted on SQL Server 2000, which is used by several thousand users across our organization, and grouped by business units. This database is evolving with each minor release, which is just about every month.

On occasion, I’m asked to merge users from one business unit into another. This is not a much problem, since it’s just a matter of searching for all instances of the business unit number and updating it with the new number.

When users in the “old” buisness unit move to the “new” unit, they must be able to access their historical data. Again, for the most part, not a problem. The catch is this: Some of the historical tables have foreign key constraints that have to be circumvented without recreating the tables.

I’m sure most, if not all of you reading this, are saying “what’s the big deal? Just look up the name of the constraint and NOCHECK it!” My problem, for which I turn to my esteemed peers, is that I want to script this merging activity, so I don’t have to do the scut-work of determining table and contraint names every time the merge is requested, because the database objects have changed.

I have a Perl script which so far is able to determine the table names that have to be updated, but what I need to know, in SQL language, is:

a) how to CASCADE updates, without modifying the tables in any kind of permanent way, or
b) how to find out if there are any constraints on a particular table, and if so, what the name is.

Once I know one of these two, I can loop through each table that the script would’ve already leanred, and update all instances of the business unit number without having SQL Server moan and complain about updating with a constraint in place.

Any help or suggestions would be greatly appreciated.

Steve.

With the following Error:
Starting MSSQLServer………………………….
Waiting for recovery. Sysmessages # 4002
[Microsoft][ODBC SQL Server Dirver][SQL Server] Login failed

I am using a Network connection between a Windows 2000 Server PC running SQL Server 2000 and a Windows NT PC running SQL Server v6.5.

There is an Error logged on the v6.5 PC indicating that the sa login failed!
EventID 17055 Mesg 1845 from MSSQLServer.

However, to get through all the earlier steps (e.g. copying across the Tables Design), it must have been able to login to the v6.5 PC via sa????

Note my 2 PCs are in different Domains, but with Trusts between them and I am logging onto both as Administrator and have set Security Permissions, for anything I think might be relevant on the v6.5 PC for the v2000 PCs Domain Administrator (and Domain Admins).

MS Article 302850 does not help.

Can anyone help with any ideas or suggestions? – This is holding me up!

Cheers