2003-08-08
2,572 reads
2003-08-08
2,572 reads
2003-08-06
2,373 reads
2003-08-04
3,110 reads
Andy returns to the Worst Practice series this week with a short article looking at how connection strings in applications affect what you see in sysprocesses. Perhaps less controversial (in our opinion) that some of the other worst practices, this is something easy to fix and definitely worth fixing! Read the article and post a comment - explore other points of view! Readers posting a comment will be entered in a drawing for a copy of the SQL Server 2000 Resource Kit.
2003-08-01
15,803 reads
2003-07-31
2,434 reads
2003-07-30
1,969 reads
2003-07-28
2,540 reads
2003-07-25
2,632 reads
2003-07-21
2,957 reads
2003-07-17
3,341 reads
By Brian Kelley
Here is a short emotional intelligence (EI) post for today, courtesy of Seth Godin....
By Steve Jones
I was recently trying to handle a simple task with a few AI tools...
A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...
Hub Via Wa:62817825533 Alamat Jl. A. Yani No.656-658, Cicaheum, Kec. Kiaracondong, Kota Bandung, Jawa...
Hub Via Wa:62817825533 Alamat Jl. Asia Afrika No.122-124, Paledang, Kec. Lengkong, Kota Bandung, Jawa...
Hub Via Wa:62817825533 Alamat: Wisma BCA BSD City, Kav. CBD, Jl. Pahlawan Seribu Lot...
The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?
See possible answers